Hand off between local, IDE, and cloud
Keep context and proof across surfaces
After this, you'll be able to move a Codex task between local, IDE, app, worktree, and cloud surfaces without losing the branch, diff, proof, or review owner.
Before you start
Complete Set a goal Codex can finish first.
The idea
A Codex handoff is not "continue somewhere else." It is a transfer of context, code state, proof, and ownership. Without those four pieces, the next surface repeats work or changes the wrong thing.
Here is the before and after: before, Codex is guessing from a loose request. After, you can move a Codex task between local, IDE, app, worktree, and cloud surfaces without losing the branch, diff, proof, or review owner.
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 (15 min)
Watch out for
- Moving to cloud with local-only context missing.
- Moving from cloud to local without applying or inspecting the actual diff.
- Continuing in another surface without naming proof already run.
- Using mobile approval as the handoff record.
Paste this into Claude
Create a Codex handoff packet: Current surface: [CLI, IDE, app, worktree, cloud, mobile] Next surface: [CLI, IDE, app, worktree, cloud, mobile] Branch or worktree: [name] Changed files: [list] Task remaining: [what is still unfinished] Proof already run: [commands or checks] Proof still needed: [commands, screenshot, review, PR] Approval boundaries: [network, secrets, deploy, auth, data] Return a handoff note another Codex surface could use without guessing.
What a good response looks like
Handoff to IDE: branch codex/profile-save, changed src/app/profile/page.tsx and src/lib/profile.ts. Remaining: inspect browser behavior and address one failing test. Proof run: npm test -- profile failed on displayName assertion. Still needed: fix test failure, run npm run build, check /profile. Do not touch auth middleware or schema.
What good looks like
- The handoff names current and next surface
- Branch or worktree state is included
- Changed files and remaining task are clear
- Proof already run and proof still needed are separated
- Approval boundaries remain explicit
When this breaks
- Breaks when the next surface starts from the wrong branch or worktree.
- Breaks when proof has to be rerun because the prior run was never recorded.
AI can help with this
Use Codex to help you you can move a Codex task between local, IDE, app, worktree, and cloud surfaces without losing the branch, diff, proof, or review owner. Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: The handoff names current and next surface. Accept only the version you can verify yourself.
You can now
You can move between Codex surfaces deliberately
- You can preserve branch and worktree state
- You can separate completed proof from pending proof
- You can keep approval boundaries visible
Key takeaways
Codex handoff is a packet, not a vibe. Transfer context, code state, proof, and ownership together.
- Handoffs need branch or worktree state.
- Changed files and remaining work must be explicit.
- Proof already run should not disappear.
- Move surfaces only when the next surface is better for the remaining job.