Codex tutorial
A bounded task
A Codex task needs an observable result. In a fictional invoice service, “repair the duplicate identifier error” becomes a useful request when you supply the failing input, the expected response and the module that owns validation. Ask the agent to preserve unrelated behavior and explain any wider change.
Use AGENTS.md for the repository’s recurring instructions. Treat secrets, customer exports and commands copied from an untrusted issue as separate decisions. A file being available does not make it appropriate to share.
Evidence at handoff
Read the diff and inspect the test named in the result. Confirm that it fails for the original reason and passes with the repair. A test command printed in a response is different from a recorded execution result. Report which checks ran and which were unavailable.
The official Codex workflow example, checked November 14, 2026, separates repository guidance from task context. The practice here uses scripted replies and fictional records. It does not launch Codex or evaluate any live model.
Continue with skill triggers when you want to reuse a workflow, and code review when the proposed patch is ready.