Open the right repo before you ask
Repo handoff before model handoff
After this, you'll be able to start Codex from the right checkout, confirm branch state, and give it the files it should inspect first.
Before you start
Complete Write a task brief Codex can finish first.
The idea
Codex cannot fix the repo you meant. It can only work in the repo you opened. Most bad coding-agent runs start with the wrong checkout, stale branch, missing dependency install, or unclear local state.
- You confirm the workingYou confirm the working directory
- You confirm the branch andYou confirm the branch and dirty file state
- You name first-read filesYou name first-read files or request a read-only inventory
- Run a repo handoff for oneRun a repo handoff for one task: location, branch, dirty files, first-read files, and
Here is the before and after: before, Codex is guessing from a loose request. After, you can start Codex from the right checkout, confirm branch state, and give it the files it should inspect first.
Now try it use the exercise prompt on one real repo task. Keep the output small enough to check before you accept the change.
You are ready when the Codex action, boundary, and proof all match the task.
Try it (10 min)
Watch out for
- Running Codex from a parent folder that contains multiple unrelated apps.
- Ignoring dirty files because they are not yours. Codex still has to work around them.
- Starting edits before Codex has named the owner files.
- Using a cloud task when the real state exists only in your local checkout.
Paste this into Claude
Prepare this repo for a Codex task: Project root: [paste pwd or project folder] Current branch: [paste branch] Known dirty files: [paste git status summary] Task: [one sentence] Files Codex should inspect first: [paths, or write unknown] Ask Codex to begin with a read-only inventory. It should return the likely owner files, a risk note, and the proof commands before editing.
What a good response looks like
Read-only inventory first. Current repo is /web/agentic-levels on branch codex/profile-save. Dirty files are src/app/profile/page.tsx and package.json. Inspect src/app/profile/page.tsx, src/lib/profile.ts, and tests/profile.test.ts before edits. Return owner files, risks, and proof commands.
What good looks like
- You confirm the working directory
- You confirm the branch and dirty file state
- You name first-read files or request a read-only inventory
- Codex does not edit until the owner files and proof are named
When this breaks
- Breaks when Codex edits a sibling package because the task started from the wrong root.
- Breaks when Codex overwrites user changes because the dirty state was never surfaced.
AI can help with this
Use Codex to help you you can start Codex from the right checkout, confirm branch state, and give it the files it should inspect first. Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: You confirm the working directory. Accept only the version you can verify yourself.
You can now
You can confirm the active repo root
- You can protect existing dirty files
- You can request read-only owner discovery
- You can hold edits until proof is named
Key takeaways
The repo handoff comes before the task. Codex quality starts with the checkout, branch, and files it can see.
- Wrong repo means wrong patch.
- Dirty files are part of the task boundary.
- Read-only owner discovery is the safest first step when paths are unknown.
- Cloud work needs a prepared environment, not hidden local state.
Go deeper