Skip to main content
Automatic switching is off until you choose it. It acts once a limit of the Claude Code account in use reaches a share you choose: 95% by default, from 50% to 99%. Under Resets Soonest, it also acts earlier, as Spend the week that resets first says. It switches early because open Claude Code sessions take up to about 33 seconds to follow, and never switches Codex, whose sessions do not follow at all. Open sessions explains both.

Turn it on

In Settings > Limits, choose Switch Automatically in When a limit reaches. Set the share in At, in its field or with its stepper, 95% at first.
The app switches only while it is open, and posts a notification for each switch. Its Switch Back switches back to the account it left, as the notice in Accounts does. On Linux, where the desktop shows no tray icon, closing the window quits Pitboard. Turn on Watch in the Background in Preferences > Advanced to go on switching, as Watch in the background says. On the command line, run pitboard watch and leave the terminal open. It switches at its own share, --at, 95 by default, and never reads the app’s When a limit reaches.
watch lists every line. The app, pitboard watch and pitboard use can run at once and never make two switches from one reading. What a switch does explains why. Anthropic’s terms may cover automatic switching: see Is this allowed.

Run it in the background

pitboard watch install starts pitboard watch in the background, and again at each sign-in, at the share you give it.
pitboard watch uninstall stops it. The watch service says what each system runs. On Linux, where systemd did not start the system, as in many containers, it refuses with schedule_unsupported. Leave pitboard watch running in a terminal instead.

Which account it switches to

Pitboard watches the account whose login Claude Code has stored, as Anthropic identifies it, not the account Claude Code’s config names. Pitboard switches to another enrolled Claude Code account with room under the share in every limit. By default, it picks the one with the most room. Which account it switches to gives every rule. If no account qualifies, nothing moves until the account runs out. The app then offers a switch by the same rules at 100%, as When an account runs out describes.

Spend the week that resets first

Anthropic resets each account’s week at a fixed time of its own, and what the account has not used of it is lost then. Resets Soonest spends that first: Pitboard picks the account whose week resets first, and switches to it before the share when it has room.
In Settings > Limits, choose Resets Soonest in Use first, under At.
On the command line, give pitboard watch the order, or give it to pitboard watch install:
An account without a weekly limit for all models, such as a Team seat, still comes first: what it leaves unused is lost at each five-hour reset. Under Notify Me, the app posts Another Account Resets First with Switch in place of switching. Before the share gives every rule.

What it never does

  • Switch back by itself once a limit reaches the share. Next time, it may choose the account it left.
  • Switch before the share to the same account twice, until that account reaches a limit or its week resets.
  • Switch before the share away from an account you put in use yourself.
  • Try an account again after its parked login failed, before the limit it was tried for resets.
  • Quit an app.

When it holds back

When Pitboard stays on the account or cannot decide, the app posts a notification and pitboard watch prints the reason. Automatic switching lists each reason and what ends it. On macOS, a run that cannot read the keychain, such as pitboard watch over SSH, fails only its own tries: see macOS says the keychain is locked. On Windows, the same holds for a run in a sign-in over SSH with a key: see Windows says Credential Manager cannot be reached. On Linux, it holds for the watch service while the login keyring is locked: see Linux says the login keyring is locked. A login file behind the keychain, or on Windows behind Credential Manager, does not stop a switch. Open sessions says when open sessions follow it.

Keep the numbers fresh

Pitboard decides from the usage it last read, so a busy session can reach the limit between two reads. Show usage in Claude Code’s status line to record each session’s usage after every response, where its periods identify the account. The app and pitboard watch see that as soon as it is written. The status line never switches.