Terms in this guide: Acceptance criteria · Context
Where Codex works affects what it can see, what it can change, and how easily you can review the result. Choose the workspace from the task’s dependencies and required state, then make that choice explicit in the brief.
Use the current checkout when state matters
A task may depend on uncommitted changes, local services, browser sessions, or files outside version control. Keep it close to that state and inspect the diff carefully so concurrent work does not become tangled.
Use isolation for independent changes
A separate worktree or clean branch helps when the task should start from a known revision and produce a self-contained change. It also gives reviews a clear comparison point.
Write down the handoff
The final note should state the starting point, changed files, checks run, and any environment-specific limitation. That record matters more than the name of the workspace.
- What repository state was required?
- Which local services or credentials were needed?
- Can the result be reviewed as a clean diff?
- Where will the final validation run?
Official references
Continue with a practical next step
Progress stays in this browser. No account needed.
Updates and upgrade guidance
- Learning context added
Added prerequisites, a suggested practice estimate, expected output, and connected definitions. The article procedure was not independently re-evaluated in this change.
What to do: Use the opening checklist to prepare. No software update is required for this editorial change.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.