I was burning through Claude session quota way too fast. So I registered another account.

Managing them with claude-swap (the command is cswap) is brilliant. It watches usage and auto-swaps the account in-flight when you hit 90%. Setup was extremely easy, and once it’s watching I don’t have to do anything; I don’t really notice anything during the session.

If you want the same setup:

  1. pipx install claude-swap
  2. Log into Claude Code with your first account and run cswap add.
  3. Don’t log out. From inside Claude Code, run /login to switch to the other account, then cswap add again. (Logging out first can revoke the refresh token stored for the account you’re leaving.)

Then start watching. cswap has to stay running in a terminal in the foreground. It does not run in the background, and the accounts do not swap unless cswap is running:

cswap auto

That polls your usage and switches to the account with the most quota left when the active one’s 5-hour or 7-day window hits 90%, while the session keeps running.

These days I skip cswap auto and just run cswap for the dashboard instead. Pick “Watch accounts” in there and it does the same thing, with the usage bars on screen while it works. That’s the dashboard in the screenshot below.

Terminal dashboard from cswap, titled watching all accounts. Two Claude accounts with live usage bars for a 5-hour window, a 7-day window, and the Fable model, plus keyboard shortcuts for switching.

The cswap dashboard: live usage for both accounts, and auto-switching.

There is one thing you do notice. When it switches, the new account has a cold cache, so the next request has to feed the entire context in again. Session usage starts with a small bump: I’ve seen 11–13% of the 5-hour quota go on the first request after a swap. How big depends entirely on the size of your context.

Categories
Tags