Token rotation (beta)

Heavy use of Claude Code can spend a week’s allowance in a day. With several subscriptions, the usual answer is to switch with /login by hand. Token rotation does that for you: each new session starts on the subscription with the most room, and a session that is about to run out moves to another one and carries on with the same conversation.

How it differs from accounts
Setting it up
Should the /login account be included?
How a subscription is chosen
When a subscription runs low
What you will see
When the subscription changes
Which cells rotate
Checking it works

How it differs from accounts

Accounts give each subscription its own config directory, so a conversation started on one stays on it. Token rotation keeps one directory (~/.claude) and changes only the credential, so every conversation can continue on any subscription — the same as switching with /login, done for you.

Setting it up

Make a token for each subscription. In your own terminal, run claude setup-token and sign in with that subscription in the browser. It prints a long token starting with sk-ant-oat01-.
Keep the token in the macOS keychain, one item per subscription:
```
security add-generic-password -a mulmoterminal -s mulmoterminal-token-personal -w
```
With nothing after -w it asks for the value, so the token never lands in your shell history. Never paste a token into a chat or into config.json. Not on a Mac? Put it in a file instead, chmod 600 it, and use "file" below — a file anyone else can read is refused.

Add tokenRotation to ~/.mulmoterminal/config.json:

"tokenRotation": {
  "enabled": true,
  "includeDefaultLogin": false,
  "tokens": [
    { "id": "personal", "label": "Personal", "email": "me@example.com", "keychain": "mulmoterminal-token-personal" },
    { "id": "work", "label": "Work", "email": "me@work.example", "keychain": "mulmoterminal-token-work" }
  ]
}

email is only for you: it is shown beside that subscription so you can tell which is which.

Settings → “Reload config file” (no restart needed).
Open a new cell, or close a cell and reopen its conversation. That is when a subscription is picked.

The mulmoterminal-model skill walks you through all of this if you ask it to “rotate my subscriptions”.

Should the `/login` account be included?

includeDefaultLogin: true adds the account you are signed into with /login as one more candidate. Once every subscription is registered as a token, set it to false: the /login account is always one of them, so it would be counted twice — and which one it is changes whenever you /login again.

How a subscription is chosen

By the 7-day window: what is left, divided by the hours until it resets. Room that is about to reset is used first, because it is lost at the reset; a subscription with a full week ahead waits. Over a week that keeps every subscription’s window draining as evenly as possible.

A subscription is skipped when its 5-hour window is at 90% or more, or its week is at 98% or more.

When a subscription runs low

At 98%: when a session finishes a turn on a subscription whose 5-hour or weekly window is at 98% or more, it moves to another one there and then — between turns, so nothing is cut off.
If it hits the limit anyway (the usage figures are a few minutes old): Claude Code reports the hit, and the session moves at once.

Either way the cell reconnects by itself and resumes the same conversation, with one line saying what happened:

[mulmoterminal] Personal (me@example.com) is close to its usage limit — continuing this conversation on Work.

The message that hit the limit is not re-sent; send it again. If every other subscription is out too, the session stays where it is, with Claude Code’s own limit message.

What you will see

The cell’s header names the subscription it runs on, with the same mark accounts use.
The toolbar’s usage gauge gets one entry per subscription; hover it for the name and address. A subscription that is out of its allowance says so instead of “no answer”.
“More features” → “Token usage” lists every subscription with what is left of its 5-hour and weekly windows and when each resets. It is in the menu only while token rotation is on.

When the subscription changes

A subscription is picked when a session’s process starts: a new cell, reopening a closed conversation, the restart button, or a move at the limit. Reloading the browser or a dropped connection reattaches the process that is already running and changes nothing.

Which cells rotate

Plain Claude cells only. A cell on a provider, a custom agent or an account already says whose subscription it runs on and is never rotated.

Checking it works

In a rotated cell, /status shows Auth token: CLAUDE_CODE_OAUTH_TOKEN.
The account Claude Code itself names (in /status and elsewhere) can still be your /login one. That is only what it read from its own settings; the usage is counted against the subscription the cell’s header names.
A token that cannot be read is skipped, with a warning naming the entry (never the token) in the server log.

Whether rotating several subscriptions suits Anthropic’s terms is yours to check.