Pitboard
Switch between your own Claude Code and Codex logins, and see how much each one has left.
With two or more Claude or ChatGPT subscriptions, changing accounts in Claude Code or OpenAI's Codex CLI means a sign-out and a browser sign-in. Pitboard keeps the login of each account you are not using, called a parked login. A switch puts the chosen account's parked login where the tool reads it.
Only the account changes: your history, sessions, settings and projects stay where they are.
A Claude Code session that is already open picks up a switch within about 33 seconds, or,
while ~/.claude/.credentials.json sits behind the keychain on macOS, when its login is next
renewed. A running codex keeps the old account until you restart it.
The menu bar app also gives each account its own window on claude.ai or chatgpt.com, signed in separately. It opens a page from your browser's Share menu as the account you choose.
Pitboard sends a login only to the service that issued it: Anthropic for Claude Code, OpenAI for Codex. It has no server of its own and no telemetry, and parked logins stay on your computer. For every request, including the app's update check on GitHub, see What leaves your machine.
Pitboard is pre-release. macOS is tested. On Linux, Pitboard builds and its tests pass, but it has not been run with a real signed-in Claude Code or Codex.
Install
The command line, on macOS and Linux:
|
The script puts pitboard in ~/.local/bin, with its man page and completions under
~/.local/share. It installs a download only when it matches the checksum its release
wrote into the script, and it changes no shell profile.
Install Pitboard has the rest, and
Verify a download says how to check the
script before you run it.
With Homebrew:
The app includes the command line and keeps both up to date, so install one or the other. Neither the script nor Homebrew needs Rust. The other ways:
- With cargo-binstall installed,
cargo binstall pitboardfetches the release's command line for your machine. - The latest release has the
command line for macOS and Linux, on x86_64 and aarch64, and the app. To check a file, use
gh attestation verify <file> --repo datlechin/pitboard, as Verify a download explains. cargo install --locked pitboardbuilds it from source, with Rust 1.91 or later and a C compiler. Without--locked, Cargo ignores theCargo.lockPitboard was released with and may pick newer dependencies.
If Homebrew installed Pitboard up to 0.3.0, follow
Upgrade from 0.3.0 or earlier.
From the old app cask, brew update replaces the app with the command line.
Run pitboard uninstall before you remove Pitboard, as
Remove Pitboard describes. Removing the
program alone leaves its parked logins, the daily renewal schedule and ~/.pitboard behind.
Quickstart
First enrol the account Claude Code is signed in to, then the others:
Before the switch, pitboard shows each account and what it has left. Each limit says how
its use compares with an even pace, and the account in use says which limit runs out first:
● personal me@example.com Max 20x signed in
5h ██████░│░░ 59% resets in 1h 10m 18% under pace
week █│█████░░░ 73% resets in 5d 18h 55% over pace
weekly limit runs out in 11h 05m at this pace
○ work me@company.com Max 20x ready · good for 26d 4h
5h █░░░│░░░░░ 12% resets in 3h 00m 28% under pace
week ████░░│░░░ 40% resets in 2d 4h 29% under pace
For Codex, put codex/ before each label: pitboard enroll codex/personal,
pitboard enroll codex/work --sign-in, pitboard use codex/work.
Do not add an account with Claude Code's /login or with codex login. Both replace the
login in use without Pitboard parking it, so the account that was in use needs a browser
sign-in again. codex login also revokes the login it replaces.
To switch in the menu bar app, click Pitboard's item in the menu bar, then choose the account. For each step and what it prints, see the Quickstart.
Documentation
Pitboard's documentation is at docs.usepitboard.com. It includes these pages:
- Quickstart
- Use Pitboard with Codex
- Show usage in Claude Code's status line
- Commands
- JSON output
- Security and privacy
- Troubleshooting
pitboard --help lists the commands. After an install with the script or Homebrew,
man pitboard describes each one.
Contributing
One person maintains Pitboard, and everyone taking part follows the code of conduct. To report a bug, use the bug report form. Report a bug says what it asks for and what is safe to paste.
For building Pitboard, working on the app and submitting a change, see CONTRIBUTING.md. Report a security problem privately, as SECURITY.md describes, and not in a public issue.
Licence
Pitboard is licensed under Apache-2.0. It is not affiliated with Anthropic or OpenAI, as NOTICE states.