Pool several coding-agent accounts behind one self-hosted proxy
A developer built two open-source proxies, one for Claude Code and one for Codex, that put multiple accounts behind a single endpoint, route by remaining quota and fail over when one hits its limit.
Source
@JamilaKhand on X · 2026-10-12
Written in our own words. Credit to the original author. Link checked 2026-10-22.
What they did
A developer built two open-source proxies, one for Claude Code and one for Codex, that put multiple accounts behind a single endpoint, route by remaining quota and fail over when one hits its limit.
Result (as claimed)
Open-sourced; no more stalls when one account runs out.
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: Pool several coding-agent accounts behind one self-hosted proxy What the original author did: A developer built two open-source proxies, one for Claude Code and one for Codex, that put multiple accounts behind a single endpoint, route by remaining quota and fail over when one hits its limit. Reported result (as claimed by the author): Open-sourced; no more stalls when one account runs out. Source: https://x.com/JamilaKhand/status/2109643408633663583 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: Pool several coding-agent accounts behind one self-hosted proxy What the original author did: A developer built two open-source proxies, one for Claude Code and one for Codex, that put multiple accounts behind a single endpoint, route by remaining quota and fail over when one hits its limit. Reported result (as claimed by the author): Open-sourced; no more stalls when one account runs out. Source: https://x.com/JamilaKhand/status/2109643408633663583 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: Pool several coding-agent accounts behind one self-hosted proxy What the original author did: A developer built two open-source proxies, one for Claude Code and one for Codex, that put multiple accounts behind a single endpoint, route by remaining quota and fail over when one hits its limit. Reported result (as claimed by the author): Open-sourced; no more stalls when one account runs out. Source: https://x.com/JamilaKhand/status/2109643408633663583 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 use Claude Code and Codex together · How to self-host AI agents on a Raspberry Pi, Mac mini or homelab · How to use AI agents for Linux, servers and homelabs
Related use cases
Send results straight from your coding agent to a teammate's agent
Instead of copying Codex output into Slack so a teammate can paste it into Claude Code, a developer built AgentDrop, an open-source tool that sends results, files and context directly from one agent to another.
Sync coding agent sessions and memory between laptops
A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store.
Check that your coding agent's improvements to an AI app are actually reliable
A team built Autoeval, an open-source tool that lets Claude Code, Codex or Cursor keep improving an AI app while measuring reliability across repeated trials and judges. Releases are gated on that evidence.
Let your next coding agent search what the last one already tried
Switching from Claude Code to Codex or Cursor meant explaining the same work again, so a developer built Agent Recall: a local, redacted index of past agent transcripts that the next agent can search.