Prepare the continuation
Both harnesses must be installed, enabled, and ready for the route and model you intend to use. Check the source task’s folder and Git changes before switching. Wait for the task to become idle; a running session cannot be moved to another provider.
- Open the existing Code session.
- Open the composer’s combined model/effort control, then its harness provider selector.
- Choose the other member of the Claude Code/Codex pair and an available model.
- Read any confirmation about drafts or queued prompts. Confirm only the work you intend to carry forward.
- In the linked destination, review the working folder, model, and permission mode. Permission mode resets to Ask; reasoning effort and fast mode also reset.
- Send your next instruction. The bounded source reference and handoff context are included when this next message is sent.
What carries forward
Rudr preserves display history and a reference to the source, while the source remains separately available. It observes Git status in the working folder; it does not copy your repository through the handoff. The destination works against its selected folder.
The handoff is not a migration of a live process, native provider memory, or native checkpoints. A visible transcript is not proof that every historical event fits in the new model context. Long references can be omitted or shortened, and the handoff should be read as context to verify rather than fresh evidence of current file contents.
Unsupported or failed switches
Other enabled harnesses can be selected for new sessions, but this existing-session switch supports only Claude Code ↔ Codex. If the selector refuses the action, confirm the source is idle and the target is ready. Preserve the source and drafts if a destination fails; do not delete them to force a retry.
Use continuation recovery, previous-session references, and remaining usage when deciding the next step.