Intelligent account routing for Claude Code.
Running Claude Code on more than one Claude account? Switchboard intelligently routes each new session to the best account, keeps it there while its cache is warm, moves it when a limit hits, and ring-fences client work to its own pool, all automatically.
Simply start claude as normal: nothing about how you work changes. Behind it, a live dashboard shows what every account has left and when it resets, Claude can read its own limits and pace its work around them, and every request is kept on record, with what it was worth.
Docs · Pools · Commands · Configuration · Troubleshooting
Every Claude plan has a weekly limit, and many have a 5-hour limit too. When an account hits one, Claude Code stops. Changing accounts by hand means quitting and signing in again, and the session resumes on a cold cache.
- Limits don't end your session. A request refused at a limit is replayed on another account before Claude Code sees the refusal. Limits and routing
- Client work keeps its accounts. Fence a pool to
~/Code/acme, and only sessions started there use the accounts in that pool. Pools - Claude paces itself. Ask Claude to spend what's left before the 08:00 reset without reaching 100%, and it spreads the work to fit. Claude and switchboard
- See when you'll run out. Runway, one of seven dashboard tabs, shows when each account runs out at your pace and when it has room again. Runway
- Every request, priced. The record keeps 400 days of requests, and sets what they'd cost at API prices against what your plans cost. Your record
- Resets arrive one at a time. Give switchboard your working day, and it starts the 5-hour window of each account at a different time. Staggered resets
Also: Notifications · Room for the Claude app · Pinning and moving · Backups and a new Mac
With one account, everything but the replay still works, because a replay needs a second account to move to.
You need macOS, Claude Code, and one or more Claude accounts.
brew install leeovery/tools/switchboardOr, with Go 1.27 or later:
go install github.com/leeovery/switchboard/cmd/switchboard@latestTo remove it, run switchboard uninstall, then brew uninstall switchboard. Your config, tokens
and record stay for a reinstall unless you add --all. See Commands.
# Add your accounts and install the rest
switchboard setup
# Start Claude Code, routed
claude
# See what every account has left
switchboard usage
# Open the live dashboard
switchboard dashboardsetup walks you through each step full screen, and makes the token for each account with
claude setup-token as it goes.
Upgrading? Run brew upgrade switchboard. The router restarts into the new version by itself
once no request is in flight. If it can't, see Troubleshooting.
- Does it read my conversations? No. It records each request without the content, and never edits a request body. Your record
- What if switchboard stops? By default,
claudesays the router is down and doesn't start. Setwhen_router_down = "direct"to start without it. Configuration - Does moving a session cost me? A move starts on a cold cache, so a session stays on its account while the cache is warm. Limits and routing
- Can I still use the Claude app? Yes. Give an account a reserve, and the router leaves that share of every window for you. Only a pin you set, or a session started without the router, spends it. Room for the Claude app
- Is it macOS only? Yes, for now. How it works
- The docs: every page, by task.
- Commands: every command and flag.
- Configuration: every config key.
- Troubleshooting: what to check when something's wrong.
Working on switchboard itself? Start with CONTRIBUTING.
MIT











