Claude Code: Pro/Max account pool automatically switches sub-agents when hitting limits
Published: 2026-10-20 · Author: AI Release · @ai_release1
⚡ The gist in 5 seconds - A project called aaronyi97/claude-pro-pool has been released — an account pool for Claude Code sub-agents. - Sub-agents are dispatched across your own Pro/Max subscriptions: selection is based on remaining quota. - When an account hits its limit, it's switched automatically, and the work continues from where it left off. ### 🔍 What was found A repository called aaronyi97/claude-pro-pool has been published on GitHub with the subtitle "Dispatch Claude Code sub-agents across your own Pro/Max accounts." The stated goal is to keep the main Claude Code conversation session from sitting idle: while the main conversation runs, child tasks (sub-agents) are dispatched to your other Pro/Max accounts. The logic is described in two points. The first is "selection by remaining quota": the account for a sub-agent is chosen based on the remaining limit, meaning the load is distributed to wherever there's still quota headroom. The second is automatic rotation: when a limit is reached (" "), the tool switches accounts and continues the run, so the main session doesn't stall at the ceiling. ### 💡 Why it matters Claude Code limits hit long runs hardest: a single session runs into the quota — and the work grinds to a halt. claude-pro-pool solves this at the level of distributing sub-agents across multiple subscriptions the user already has, without any third-party API keys. The practical value is continuity for long tasks and even quota usage across all accounts at once; those who need more usually look toward Anthropic's enterprise plans.
⚡ The gist in 5 seconds - A project called aaronyi97/claude-pro-pool has been released — an account pool for Claude Code sub-agents.
- Sub-agents are dispatched across your own Pro/Max subscriptions: selection is based on remaining quota.
- When an account hits its limit, it's switched automatically, and the work continues from where it left off.
🔍 What was found A repository called aaronyi97/claude-pro-pool has been published on GitHub with the subtitle "Dispatch Claude Code sub-agents across your own Pro/Max accounts." The stated goal is to keep the main Claude Code conversation session from sitting idle: while the main conversation runs, child tasks (sub-agents) are dispatched to your other Pro/Max accounts.
The logic is described in two points.
The first is "selection by remaining quota": the account for a sub-agent is chosen based on the remaining limit, meaning the load is distributed to wherever there's still quota headroom.
The second is automatic rotation: when a limit is reached (" "), the tool switches accounts and continues the run, so the main session doesn't stall at the ceiling.
💡 Why it matters Claude Code limits hit long runs hardest: a single session runs into the quota — and the work grinds to a halt.