Codex
Pitboard reads the account from the login itself, with no request, as read in Codex 0.154.0.Claude Code
Pitboard asks Anthropic, because Claude Code’s config can name another account than the login’s. As read in Claude Code 2.1.294, a sign-in writes its account there. So does any process that starts whileprofileFetchedAt is missing or over 24 hours old. A switch removes that field, so a process started on another login, as over SSH, writes that login’s account.
Pitboard records each answer with the login’s fingerprint, and asks again only once that changes, as after a renewal or a sign-in. A switch and pitboard forget also ask once it has changed. Reads that send no request, such as pitboard status --offline, use the record.
When the config has named another account since Anthropic last answered, something may have signed in. Reads that send no request then warn with in_use_unconfirmed. pitboard status settles it, and the app starts such a read once by itself.
Claude Desktop
Pitboard asks claude.ai nothing, and knows a login by a fingerprint of its session cookie. Claude Desktop logins says how.A lapsed login in use
Pitboard never asks Anthropic to identify a login with an expired access token. Where it must ask and that token has expired, it renews Claude Code’s login first. Claude Code renews its login only while a session uses it, and a login file behind the keychain can keep every session off it. As read in 2.1.294, Pitboard renews it as Claude Code does. It takes the lock a session takes to renew, and reads the login again under it. A login a session renewed meanwhile is asked about as it is. Otherwise Pitboard sends the refresh token, and saves the answer only where the stored login still holds that token. Until the answer is saved, a copy waits in Pitboard’s store. If Pitboard stops first or the save fails, the next change saves it, or the next read that must identify the login. While the copy waits, no change renews, parks, replaces or puts away that login. Each stops and says why. On macOS, Pitboard’s store is the keychain that holds Claude Code’s login. If the keychain is locked before Pitboard sends the refresh token, Pitboard sends nothing. Where macOS cannot ask for your password, as over SSH, a keychain that locks while Anthropic answers takes neither the copy nor the answer, and the stored login stops working. A change then says to runclaude and sign in, and a read marks the account in use login_refused.
A read renews the login only while no other Pitboard command runs. Asking for usage never renews it.
If Anthropic no longer accepts the login, Pitboard changes nothing. A change stops with session_expired, and a read marks the account in use login_refused.
When Pitboard renews a login in use
Pitboard renews a login a tool may be using in three cases only:- A change or a read renews Claude Code’s login in use where it must identify it, as A lapsed login in use describes.
pitboard stowrenews one it puts away with an expired access token.- A warm-up of the account in use renews its login where the access token would lapse within 5 minutes.