explaingit

dhkts1/teamclaude-rs

Analysis updated 2026-05-18

5RustAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A Rust command line proxy that spreads Claude API requests across multiple accounts and shows their usage in a live terminal dashboard.

Mindmap

mindmap
  root((teamclaude-rs))
    What it does
      Rotates requests across accounts
      Refreshes OAuth tokens
      Live terminal usage dashboard
    Tech stack
      Rust
      Cargo
      Local JSON config
    Key features
      Least recently used rotation
      Zero spend quota checks
      Optional session affinity
    Use cases
      Balance load across Claude accounts
      Avoid hitting one account rate limit
      Monitor account usage live
    Audience
      Developers using Claude Code
      Power users with multiple accounts
      Rust developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Spread Claude Code requests across several personal accounts to avoid rate limits.

USE CASE 2

Monitor live usage and quota status for multiple Claude accounts in a terminal.

USE CASE 3

Run a local forward proxy that only intercepts Anthropic API traffic.

USE CASE 4

Keep a work session's response cache warm by pinning it to one account.

What is it built with?

RustCargoTUI

How does it compare?

dhkts1/teamclaude-rseternal-flame-ad/unitdc-rsmadeye/mcp-distill
Stars555
LanguageRustRustRust
Last pushed2024-10-12
MaintenanceStale
Setup difficultyeasymoderatemoderate
Complexity2/52/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 30min

Requires Rust's Cargo build tool and existing Anthropic OAuth accounts to add via tcr login.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

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.

Copy-paste prompts

Prompt 1
Walk me through installing teamclaude-rs with Cargo and adding tcr to my PATH.
Prompt 2
Help me write a teamclaude.json config file with two accounts and different priorities.
Prompt 3
Explain the difference between base-URL mode and forward-proxy mode in teamclaude-rs.
Prompt 4
Explain what sessionAffinity and warmupSeconds do in teamclaude-rs and when to enable them.

Frequently asked questions

What is teamclaude-rs?

A Rust command line proxy that spreads Claude API requests across multiple accounts and shows their usage in a live terminal dashboard.

What language is teamclaude-rs written in?

Mainly Rust. The stack also includes Rust, Cargo, TUI.

What license does teamclaude-rs use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is teamclaude-rs to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is teamclaude-rs for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.