ABOUTCODEX / GLOSSARY
Codex terms, in plain language
Short definitions with a practical next step. Find the word, then see how it is used.
- Acceptance criteria#
Observable conditions that tell a reviewer whether a task is finished.
See it in practice →- Agent#
An assistant that can use tools and act on a task within the access and instructions it has been given.
See it in practice →- AGENTS.md#
A Markdown file for project instructions, such as conventions, commands, and review expectations.
See it in practice →- Artifact#
A concrete output you can inspect or reuse: a patch, report, document, or downloadable package.
See it in practice →- Context#
The task instructions, files, conversation, and tool results available to the assistant for a particular request.
See it in practice →- Diff#
A comparison that shows what changed between two versions of files.
See it in practice →- Evaluation#
A recorded check against defined tasks and criteria. A scoped result is evidence for those tasks, not a guarantee for every use.
See it in practice →- Fixture#
A controlled example used to reproduce a behavior or practise a workflow.
See it in practice →- MCP#
Model Context Protocol: a way for compatible applications to connect to tools and data supplied by servers.
See it in practice →- Permission#
Access to read, write, execute, or connect to something. Check the scope required by a task.
See it in practice →- Plugin#
A packaged extension that can combine capabilities such as skills and connections. Inspect what a package includes.
See it in practice →- Prompt#
The request and constraints you give an assistant for a task.
See it in practice →- Regression#
A previously working behavior that breaks after a change.
See it in practice →- Repository#
A project’s files and version history, commonly managed with Git.
See it in practice →- Skill#
A reusable procedure defined by instructions and optional supporting files for a focused kind of task.
See it in practice →- Verification#
Checking an actual result against the expected behavior and recording evidence.
See it in practice →- Worktree#
A separate Git working directory connected to the same repository, useful for keeping work isolated.
See it in practice →
Plain-language editorial definitions. For specifications and current product behavior, consult the official skill documentation, Git documentation, and MCP documentation.