Hand a session off from Claude Code to Codex when you hit a limit
A developer who switches between Codex and Claude Code depending on the task and remaining usage built a tool to hand a session from one to the other, so running out of usage mid-task does not lose the work.
Source
@johnjianwang on X · 2026-10-20
Written in our own words. Credit to the original author. Link checked 2026-10-22.
What they did
A developer who switches between Codex and Claude Code depending on the task and remaining usage built a tool to hand a session from one to the other, so running out of usage mid-task does not lose the work.
Result (as claimed)
He can continue the same task in the other agent instead of starting again.
Tools they used
Cost: Claude Code: from $17/mo; OpenAI Codex: free plan, paid from $8/mo.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Claude Code, OpenAI Codex. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Hand a session off from Claude Code to Codex when you hit a limit What the original author did: A developer who switches between Codex and Claude Code depending on the task and remaining usage built a tool to hand a session from one to the other, so running out of usage mid-task does not lose the work. Reported result (as claimed by the author): He can continue the same task in the other agent instead of starting again. Source: https://x.com/johnjianwang/status/2112598049650569550 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Hand a session off from Claude Code to Codex when you hit a limit What the original author did: A developer who switches between Codex and Claude Code depending on the task and remaining usage built a tool to hand a session from one to the other, so running out of usage mid-task does not lose the work. Reported result (as claimed by the author): He can continue the same task in the other agent instead of starting again. Source: https://x.com/johnjianwang/status/2112598049650569550 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Hand a session off from Claude Code to Codex when you hit a limit What the original author did: A developer who switches between Codex and Claude Code depending on the task and remaining usage built a tool to hand a session from one to the other, so running out of usage mid-task does not lose the work. Reported result (as claimed by the author): He can continue the same task in the other agent instead of starting again. Source: https://x.com/johnjianwang/status/2112598049650569550 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to vibe code an app with Claude Code · How to save, share and resume coding agent sessions · How to use Claude Code and Codex together · How to run multiple coding agents together
Related use cases
Move a live Claude Code session from your desk to your laptop
onthego moves your uncommitted changes and your Claude Code or Codex session to another machine with one command, so you can resume mid-thought away from your desk.
Put Claude Code, Codex and Gemini in one terminal list with live status
A developer built agent manager, a local terminal app that connects to the subscriptions and tools you already have. Instead of separate tabs where one agent sits on an unseen permission prompt, every session appears in one list with live status.
Keep one memory across Claude Code, Codex and Cursor when you switch tools
Two founders kept switching coding agents whenever usage limits ran out or a better model came out, and had to re-explain tasks, workflows and past mistakes each time. They built an open-source, cross-harness memory layer the agents share.
See your Claude Code and Codex limits in your Mac menu bar
Tired of hitting limits mid-task, he built Pikori, a small Mac menu bar app showing Claude Code and Codex 5-hour and weekly limits and reset times, with a pixel buddy that gets nervous as you run low.