One command. All your Claude accounts.

It’s 4 p.m., the refactor is half-landed, and Claude Code stops mid-thought: the 5-hour window just closed. So you type /login, squint at the account picker, swap to the other subscription, and try to remember where you were.

If you keep two or three Claude Max plans around precisely for this moment, you know the ritual. The plans aren’t the problem — the swapping is. Routing is a job for software, not for muscle memory.

Claude Code keys its credentials off a single environment variable. Each distinct CLAUDE_CONFIG_DIR gets its own isolated macOS Keychain login — so cr keeps one directory per account, and on every launch it:

1. picks an account by policy — or your forced --account,
2. unsets ANTHROPIC_API_KEY and friends, which would otherwise override your subscription login,
3. points CLAUDE_CONFIG_DIR at the chosen account,
4. prints a one-line banner to stderr, and
5. execs the real claude — TTY, signals, and exit code pass straight through, with zero overhead.

Three lines to install, one browser login per account. macOS-first, because Keychain isolation is the clean path there; it runs on Linux too, where credentials come from .credentials.json instead. The only hard dependency is jq.

Then teach it your accounts. Your existing ~/.claude login is adopted as default — never moved, never modified.

From here on, type cr wherever you typed claude. Anything it doesn’t recognize is forwarded verbatim — flags, prompts, --resume, all of it. The only visible difference is one quiet line saying who’s at the helm.

Four ways to pick the next account:

Pin one with cr use work when you want stillness; force a single launch with cr@work when you don’t.

cr usage draws how much is left in each window — the 5-hour session, the 7-day total — with reset countdowns, so you can see at a glance which subscription to lean on.

And every policy skips exhausted accounts. Before routing, cr refreshes stale usage data and drops any account at or above the exhaustion threshold from the rotation — a maxed-out subscription is never chosen. If every account is spent, it falls back to the full set rather than failing. Tune it to taste:

Routing well at launch still leaves one wall: the account you’re on can run dry mid-session. Add --watch (or -w) and cr stays at the helm — a background watcher polls usage, and when the account in use crosses the threshold (90% by default) while another has headroom, it waits for a quiet moment, then restarts Claude Code under the fresher account with --resume. The conversation follows; you lose a few seconds of restart, not your context.

Honest fine print: a reply can’t be handed off mid-stream — the watcher waits until the session has been idle for a beat (30 seconds by default) before it moves. Tune all three knobs: