KarpelesLab/teamclaude

What it solves

TeamClaude (also known as TeamRouter) solves the problem of hitting usage limits when running multiple AI coding agents simultaneously. It acts as a local proxy that manages a pool of your own subscription accounts, automatically rotating between them when an account hits its session or weekly quota, allowing long-running agent tasks to continue without interruption.

How it works

The project sits between your coding agent (like Claude Code or the Codex CLI) and the provider's API. It monitors response headers to track quota usage for each account in your pool. When an account nears its limit, the proxy transparently switches to the next available account. It handles OAuth token refreshes, manages per-account network routing, and provides a terminal-based interface (TUI) to monitor usage, reset countdowns, and manage account priority.

Who it’s for

This tool is designed for individual power users who run many concurrent AI coding sessions and possess multiple subscription accounts. It is intended for personal use to manage one's own credentials and is not a service for sharing accounts or reselling access.

Highlights

• Automatically rotates across multiple accounts to bypass 429 rate-limit errors.
• Tracks separate quota buckets for different models and time windows (5-hour/7-day).
• Includes a live TUI to monitor quota, activity logs, and proxy status.
• Supports per-account network routing (e.g., SOCKS5 proxies) for individual accounts.
• Allows for "holding" requests until quota resets, enabling unattended long-running tasks.
• Provides an optional MCP endpoint for agents to query or manage the proxy fleet directly.