The quick read
- For an illustrative search bug, ask for the smallest coherent repair and a check using the previously failing query.
- Read the changed files and the explanation of why they solve the problem.
Write the acceptance criteria
Describe the existing behaviour, desired behaviour and boundaries of the task. Include relevant files or reproduction steps when known. Let the agent inspect the repository’s own instructions and established patterns before choosing an implementation.
Keep actions understandable
For an illustrative search bug, ask for the smallest coherent repair and a check using the previously failing query. Separate local code changes from external actions such as deploying or sending messages, using the permissions and workflow appropriate to the environment.
Assess the result
Read the changed files and the explanation of why they solve the problem. Confirm which checks ran successfully and which remain unavailable. Do not treat a generated test as proof merely because it mirrors the new implementation. OpenAI’s official Codex page describes the product; exact capabilities depend on the interface and setup in use. The practical standard is a maintainable change with evidence tied to the requested behaviour, rather than a large patch produced quickly.
Sources & notes
Source-based guide, not a hands-on product test. Features and availability can change.
openai.com — official reference
Sources reviewed for the September 2026 launch edition.