tokenmaxxing
Automatic Claude Code account switching - pool your own subscription accounts and hot-swap credentials when quota fills, keeping every session continuable.
tokenmaxxing is a CLI for automatic Claude Code account switching. It pools multiple subscription (Pro/Max) accounts that you own and hot-swaps the active credential to a fresher account when the one in use nears a usage limit. You run claude exactly as you always do; the swap happens at a safe turn boundary and your running session continues the same conversation on the new account without restarting. It works across many concurrent sessions at once.
The only visible behavior is the worst case: when the whole pool is at its limit, the session pauses with a countdown and auto-resumes on the next account to reset (Ctrl-C resumes immediately).
Scope: Claude Code on macOS and Linux, plus OpenAI's Codex CLI as a second, parallel pool. It pools subscription accounts, not API keys. This is a personal-use tool for pooling accounts you own, in sessions and agents you run yourself - see Personal use and terms of service.
The problem
A Claude subscription meters three limits at once (all confirmed via /usage):
- Current session: a rolling 5-hour window.
- Current week (all models): a 7-day aggregate.
- Current week, per model: separate weekly caps for individual model families. These currently exist only for Sonnet and Fable, and only the Fable cap is tight enough to matter - it binds well before the aggregate does. A machine can sit at 50% week-all while already at 80% week-Fable.
Weekly quota is use-it-or-lose-it: whatever an account has not consumed by its fixed weekly reset is forfeited. If you own several accounts, the rational strategy is to keep burning quota on whichever account is furthest behind its own weekly pace, and to switch away before any single limit hits the wall mid-session.
Doing that by hand means logging out, logging in, and losing your conversation. tokenmaxxing automates it: a running claude re-checks its credential store between requests, so a credential swapped underneath it is adopted in place (within about 30 seconds on macOS, on the next request on Linux). A plain swap never restarts your session. The one case that still needs process management is a fully depleted pool - a session cannot pause itself - and that is what the thin supervisor exists for.
Everything else about claude is unchanged: all flags, MCP servers, hooks, and skills pass through.