Skip to main content

​
Check first

Do not switch accounts while any check shows ✗, broken. doctor lists every check and mark. pitboard log lists the last changes and how each ended. In the app, Diagnostics makes the same checks, and Activity shows the log. On macOS, both are in the Window menu. On Windows, they are in Settings > Troubleshoot. On Linux, they are in the Pitboard window’s main menu. Error and warning codes gives the cause and fix of each code a message names. These pages cover the rest:

​
Claude Code over SSH uses another account

A Claude Code session started over SSH can stay on another account than Pitboard shows, through every switch, and Pitboard warns with fallback_login. On Linux, Claude Code keeps its login only in ~/.claude/.credentials.json, which every session reads, so a session over SSH follows a switch too.
A /login while the keychain is locked, as over SSH, writes the login to ~/.claude/.credentials.json, which such a session signs in with. A login file behind the keychain or Credential Manager says what else it does.
  1. In a desktop terminal, where the keychain is unlocked, run pitboard stow, or click Clean Up on the app’s notice A leftover sign-in file. A session signed in with the file is signed out.
  2. Before you start Claude Code over SSH, run security unlock-keychain ~/Library/Keychains/login.keychain-db, or start it from a desktop terminal. Do not run /login while the keychain is locked.
If stow cannot read the file, make it readable to you, or delete .credentials.json, login and all.

​
An account reads login replaced outside Pitboard

The only login of the account in use ended outside Pitboard. A sign-in such as /login or codex login wrote over it, or the account was signed out in Claude. Pitboard held no copy, so that login is gone, and every read warns with login_replaced. Sign in to the account again, or forget it. To add another account without ending the login in use, follow Add another account.

​
Smart App Control blocks Pitboard

On Windows, Smart App Control blocks unsigned apps that Microsoft’s cloud service cannot vouch for, and cannot allow a single app, as Microsoft’s What is Smart App Control says. With Smart App Control on, Windows opened Pitboard’s unsigned installer and command line with no prompt, measured on 18 October 2026 on Windows 11 build 26300. Whether Smart App Control lets the app start has not been measured. The app loads WinSparkle.dll, which no release signs: see the code signing policy.
Microsoft’s page says recent Windows updates let you turn Smart App Control on again, and names none of them. On a Windows without them, it turns on again only after a clean installation of Windows.
To run a Pitboard file it blocks, open Windows Security, select App & browser control > Smart App Control settings, then Off.

​
Report a problem

Open a GitHub issue with:
  • What you ran, what it printed and what you expected.
  • The output of pitboard doctor --json, not plain pitboard doctor: it hides email addresses, account identifiers and your home.
  • pitboard --version, and claude --version or codex --version.
  • How you installed Pitboard, and your macOS version. On Linux, give the distribution, its version and the desktop, such as Fedora 44 with GNOME. On Windows, give the build and the system type, x64 or ARM64, which Settings > System > About shows.
  • The last lines of pitboard log, if they help. A reclaim line can name an account identifier.
For a security problem, follow Report a vulnerability.