Load-balancing Claude Code subscriptions
Why I built a load balancer across multiple Claude Code subscriptions.
🌳 Evergreen Planted 2026-06-01 Last tended 2026-06-16
Running many Claude Code agents against a single subscription hits rate limits fast. The fix that stuck: a small auto-balancer that spreads work across several subscription accounts, scoring each account by remaining headroom and reset proximity rather than picking by a hard threshold.
The key design lesson — no threshold cliffs in the scoring function. An account six hours from reset shouldn’t score zero while one at 29 minutes gets full credit. Every term is a smooth function of its inputs (a single time-constant decay), not a bucketed policy guess.
I wrote this up in full on the blog: I Built a Load Balancer for My Claude Code Subscriptions.
Open threads
- Cross-machine fairness when the same account is shared across boxes.
- Whether reset-proximity should decay on a per-account or per-pool basis.