Claustrophobic, a multi-account harness for Claude Code
Sessions persist across Claude accounts when one hits rate limits.
Using math to pay less for Claude
Clever rate-limit arbitrage via pre-activation scheduling, but only works if you own multiple accounts.
Heavy Claude Code users hitting the 5-hour Pro rate limit; those running multiple accounts already
I built this tool specifically for Claude Code users who hit the 5-hour rate limit wall mid-flow. There's no official plan between Pro ($20/mo) and Max ($100/mo). it's a fixed gap with nothing in between.
The workaround most people do manually: running multiple Pro accounts and switching when one is limited. This actually works, but naive rotation wastes a lot of capacity. When you activate an account turns out to matter as much as which one you use. A single throwaway prompt sent a few hours before your coding session can unlock an extra full cycle.
PolyClaude automates this. You tell it your accounts, your typical coding hours, and how long you usually take to hit the limit. It uses combinatorial optimization to compute the exact pre-activation schedule, then installs cron jobs to fire those prompts automatically. When you sit down to work, your accounts are already aligned.
It's free and open source. Install is one curl command, then an interactive setup wizard handles the rest.
Repo: https://github.com/ArmanJR/PolyClaude
Hope you find it useful!
Sessions persist across Claude accounts when one hits rate limits.
Workaround for Anthropic's lack of multi-account support; niche pain with limited appeal.
Automatic account failover + Slack remote access for Claude Code, no servers.
Predictive account switching beats waiting for rate-limit errors on multiple Claude subscriptions.
Yet another cloud cost optimizer competing with Vantage, CloudHealth, and Azure Cost Management.
Reads ~/.claude/ JSONL directly instead of terminal scraping, works with Kitty and iTerm2.