dhkts1/teamclaude-rs — explained in plain English
Analysis updated 2026-05-18
Spread Claude Code requests across several personal accounts to avoid rate limits.
Monitor live usage and quota status for multiple Claude accounts in a terminal.
Run a local forward proxy that only intercepts Anthropic API traffic.
Keep a work session's response cache warm by pinning it to one account.
| dhkts1/teamclaude-rs | eternal-flame-ad/unitdc-rs | madeye/mcp-distill | |
|---|---|---|---|
| Stars | 5 | 5 | 5 |
| Language | Rust | Rust | Rust |
| Last pushed | — | 2024-10-12 | — |
| Maintenance | — | Stale | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 2/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Rust's Cargo build tool and existing Anthropic OAuth accounts to add via tcr login.
teamclaude-rs, run from the command line as tcr, is a small local proxy tool that sits between Claude Code, or any other tool that talks to Anthropic's API, and multiple Claude accounts you own. Instead of pointing your tool at one account, you point it at this proxy, and it spreads your requests across several accounts automatically, refreshing each account's login token as needed, while showing a live terminal dashboard of how close each account is to its usage limit. It is a full rewrite in Rust of an existing Node.js project called teamclaude, built to use the same configuration file format and certificates so it can be swapped in on the same port without changing setup. The tool picks which account to use next by choosing whichever account was used least recently, while still respecting a priority order you set, so backup accounts are only used once your main ones are close to their limits. It can be used two ways: either by setting an environment variable that points your client straight at the proxy, or by running it as a forward proxy that only intercepts and decrypts traffic to Anthropic's API while passing every other website through untouched. It checks each account's usage by calling a usage endpoint that does not itself count against your message quota, so the live dashboard stays accurate even when accounts are sitting idle. Two optional settings can be turned on in the config file: one keeps a single work session pinned to the same account so that account's response cache stays warm, and another periodically pings idle accounts to keep their usage window active, though this second option does use real quota, so it is off by default. The proxy only listens on the local machine, so no outside network access is possible, and it includes a pre commit hook that scans for accidentally committed secrets. Setup requires Rust's Cargo build tool, and configuration is stored in a local JSON file that is written with restricted file permissions. The project is released under the MIT license.
A Rust command line proxy that spreads Claude API requests across multiple accounts and shows their usage in a live terminal dashboard.
Mainly Rust. The stack also includes Rust, Cargo, TUI.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.