go-claude-swap

A Go rewrite of claude-swap — a multi-account manager for Claude Code. Switch between Claude accounts without logging out, watch usage across all of them, and rotate automatically when the active account approaches its rate limits.

Single static binary (cswap), no Python runtime required.

brew install blairham/tap/cswap

Or with Go:

go install github.com/blairham/go-claude-swap/cmd/cswap@latest

Or from a clone:

make build   # → build/cswap
make install

# While logged in to Claude Code as account A:
cswap add

# Log in as account B (claude /login), then:
cswap add

# See everyone's usage:
cswap list

# Switch:
cswap switch 2        # by slot
cswap switch work     # by alias
cswap switch          # rotate to the next account

# Live dashboard:
cswap tui

# Hands-off rotation at 90% utilization:
cswap auto

# ...or run it always-on (starts at login, restarts on crash):
brew services start cswap     # Homebrew installs
cswap service install         # any install: launchd (macOS) / systemd --user (Linux)

Most read commands take --json for scripting; cswap auto --json emits JSONL events.

• Credentials: on macOS the Keychain item Claude Code itself uses (Claude Code-credentials) is swapped; on Linux/WSL it's ~/.claude/.credentials.json. Per-account backups live in the Keychain (macOS) or as files under the backup root.
• Config: only the oauthAccount object inside ~/.claude.json is spliced per account — projects, MCP servers, and all other machine state are preserved.
• MCP logins survive: machine-shared credential fields (mcpOAuth, pluginSecrets, …) always follow the live machine state, not the slot.
• Safety: switches hold Claude Code's own credential locks (the proper-lockfile protocol) so a concurrent token refresh can't collide; all writes are atomic; a failed switch rolls back; displaced credentials are stashed (cswap unclaimed), never discarded.
• Auto-switch: cswap auto polls usage adaptively (respecting the endpoint's request budget with backoff and reset-aligned scheduling) and switches proactively — before the limit — so a running Claude Code picks up the new credential while the old one still works.
• Model-aware: the binding window is the worst of 5h, 7d, and the watched models' weekly limits. By default (autoswitch.model auto) cswap watches the model Claude Code is currently using — $ANTHROPIC_MODEL, then the model key in ~/.claude/settings.json — re-detected on every poll. So when you're on Fable and an account's Fable weekly window fills up, the rotation lands on the account with the most Fable headroom left, even if the exhausted account's overall 7d window still looks healthy.
• Service ⟷ TUI over gRPC: a looping cswap auto serves a control API (pkg/swapapi) on a unix socket in the backup root. The TUI connects to it for status, streams switch events live, and goes store-only while the service is running — one process owns the usage-request budget, and the dashboard reads its results from the shared cache.

Data lives in ~/.claude-swap-backup (macOS) or ${XDG_DATA_HOME:-~/.local/share}/claude-swap (Linux/WSL) — the same layout as the original claude-swap, so both tools can coexist.

cswap config set autoswitch.threshold 85
cswap config set autoswitch.strategy consume-first
cswap config set autoswitch.model auto         # follow Claude Code's model (default)
cswap config set autoswitch.model Fable,Opus   # or pin the watched weekly limits
cswap config set autoswitch.model none         # 5h/7d windows only
cswap config set ui.theme light

Session mode (cswap run), directory mappings, setup-token accounts (add-token), the macOS menubar extra, and the deepest edge-case machinery of the original (consume-gate CAS persistence, provenance oracle probing).

make check    # fmt + vet + test
make lint     # golangci-lint
pre-commit install

MIT. A from-scratch Go rewrite of realiti4/claude-swap (MIT) — the storage layout, lock protocols, and switching semantics follow the original so the two stay compatible on disk.