Account pooling. Pooling several subscriptions into one supply may conflict with the terms of the providers you use, so check those terms before you set it up.
Who it is forA developer in the middle of a long Claude Code task who keeps hitting the usage limit on one subscription.
The problemWhen one account runs out, the session stops and the manual workaround means logging out, logging into another account and pasting a handover note.
The outcomeThe session continues on the next account between requests, with the same context and terminal.
What you need first
- Python 3.10+, git, and the claude CLI on your PATH
- At least two accounts to pool: Claude Pro or Max, ChatGPT/Codex, or Anthropic API keys
- A browser to complete the account login
- macOS is the most tested platform; Windows and Linux are best-effort per the README
Steps
- Install with the one-line command for your system from the README Install section, then open http://127.0.0.1:4317/ to confirm the dashboard runs.
- Run
claude-unlimited add-accountto log in your first Claude Pro or Max account in the browser. - Add a second account, such as a ChatGPT/Codex subscription or an API key, from the dashboard at http://127.0.0.1:4317/.
- Run
claude-unlimited codein your project and keep working as normal. - Check the dashboard activity log to see when a switch happened.
Prompt for your agent
Using the DevDock-AI/claude-unlimited repo, install the daemon and add a second account, then start a Claude Code session with `claude-unlimited code` in <project-path>. Expected output: the dashboard at http://127.0.0.1:4317/ lists at least two accounts. Verify that the dashboard shows both accounts and that the session starts without an error.
Caveat. The README says Windows and Linux are best-effort and macOS is the most tested platform.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page