Skip to main content

​
Add it to Claude Code

pitboard must be on the PATH Claude Code runs the line with. If you installed only the app on macOS, first put its command line on your PATH, as Install the app shows. On Windows, the installer puts it there for terminals opened after it ran. Add a statusLine field to Claude Code’s settings.json, beside the fields already there. It is in ~/.claude, or in the folder CLAUDE_CONFIG_DIR names. On Windows, ~ is your user folder, such as C:\Users\me.
~/.claude/settings.json
If the file already has a statusLine, combine it with your own status line instead. Claude Code runs the command after each response. On macOS and Linux, it runs in your shell. On Windows, Claude Code runs it in Git Bash where it finds one, then in PowerShell 7, then in Windows PowerShell: read in Claude Code 2.1.301, and measured with 2.1.302. pitboard statusline runs the same in each. The status line line of pitboard doctor names the one Claude Code uses. Where it says no pitboard is on its PATH, add the folder pitboard.exe is in to your PATH, then start Claude Code again.

​
Read the line

Each session shows a line such as:
  • The account the session is on comes first, in bold.
  • Every other Claude Code account you enrolled follows it.
  • Each account shows how much of its five-hour limit is used, then its weekly limit. An account without a weekly limit for all models, such as a Team seat, shows its five-hour limit alone.
  • A red ▲ after a percentage of the first account means that limit is used faster than an even pace.
  • A green ▼ means slower.
Until the session’s first response, the line shows the account in use first, with Pitboard’s last reading of it. The line leaves out accounts of OpenAI’s Codex CLI and limits for a single model. Check what each account has left shows them. Every mark, label and colour, such as ?, work? and unenrolled, is listed under statusline.

​
Combine it with your own status line

If your status line script runs in bash and reads its input with input=$(cat), add this line to it:
If it runs in PowerShell, read its input with $json = $input | Out-String, and parse $json for its fields. Then add this line to it:
Pass the input unchanged: Pitboard reads the session’s session_id and usage from it. Without session_id, it prints the line but records none of the session’s usage. Which account a session records for says when Pitboard records a session’s usage, and for which account.