Claude Code shows another account than Pitboard
/status in Claude Code shows the account its config names. Pitboard shows the account whose login is stored, which requests use. A sign-in, or a session started on another login, can write another account into the config: see How Pitboard knows whose login it is.
Pitboard warns with the cause, such as config_names_another or in_use_unconfirmed, and Warning codes gives each fix.
After a switch, an open session keeps the old account and its /usage for up to about 33 seconds. While a login file sits behind the keychain, it keeps them until its next renewal: see Claude Code over SSH uses another account.
macOS says the keychain is locked
Where macOS cannot ask for your password, as over SSH, a locked keychain stops Pitboard withcredential_store_locked:
pitboard doctor marks each parked login not read: the keychain is locked. Those parked logins need no sign-in.
Codex keeps the old account
Everything that runs Codex keeps its account until it starts again. Restart what runs Codex says how to restart each without losing a login. If the switch refused Codex’s login store, see Before you enrol a Codex account.A parked login has expired
pitboard status shows login expired beside the account, and Pitboard’s menu shows Needs signing in again. Sign in to the account again, then turn on daily renewal to keep it from happening.
Usage shows old numbers
Old numbers carry their age and often a reason, as inmeasured 14:02, 3m ago · Anthropic could not be reached. Stale codes says what to do about each reason.
With no reason, Pitboard asked moments ago, and waits 3 minutes for a five-hour limit. pitboard status --fresh, or Refresh in the app, asks anyway.
Pitboard cannot find a tool
The command line says:PATH, or set PITBOARD_CLAUDE or PITBOARD_CODEX to its path.
The app looks for claude and codex on your login shell’s PATH, then in ~/.local/bin, /opt/homebrew/bin and /usr/local/bin. It looks each time the dialog opens and each time Pitboard comes to the front, so return to the dialog after you install. It sees PITBOARD_CLAUDE and PITBOARD_CODEX only when launchctl setenv set them.
Daily renewal stopped working
pitboard doctor flags its renewal schedule line:
Turn Renew parked logins daily off and on in Settings > Renewal, or run:
The schedule uses another proxy
pitboard doctor warns on its renewal schedule's proxy line when the schedule’s proxy differs from your shell’s. Run pitboard schedule install from a shell where the proxy variables are right.
In the app, turning Renew parked logins daily off and on gives the schedule only the proxy variables launchctl setenv set.