Skip to main content

​
What you need

The app includes the command line, so install one or the other. On an older Windows, Pitboard changes nothing. You also need Claude Code, OpenAI’s Codex CLI or Claude Desktop, signed in to one of your accounts. Claude Desktop accounts need macOS: read Before you add a Claude Desktop account first. Pitboard for Windows is in beta, and its files are not signed. It was run with real Claude Code logins on 18 October 2026, with Claude Code 2.1.302. Codex sign-ins and switches on Windows have not been measured. On Linux, Pitboard was run with real Claude Code and Codex logins on 30 October 2026, with Claude Code 2.1.314 and Codex 0.166.0, on Fedora 44 with GNOME and with KDE Plasma, Ubuntu 26.04 and Debian 13.

​
Install the app

Download the app from Download Pitboard, then move Pitboard.app to your Applications folder before you open it. Until then, macOS runs it from a temporary copy, and the app cannot turn on daily renewal or link its command line.Or install it with Homebrew. The pitboard-app cask also puts the app’s command line on your PATH, with its man page and completions:
Without the cask, put the app’s command line on your PATH from Settings > Advanced, under Command Line: click Install Command Line Tool, then enter an administrator’s password when macOS asks. It then updates with the app. Command line says when the button shows. You can also run /Applications/Pitboard.app/Contents/Helpers/pitboard.

​
Install with the script

On macOS, or on a Linux distribution Pitboard’s repository does not cover, the install script installs the command line:
The install script says where it puts each file, what it needs and how to choose another folder.

​
Install with Homebrew

On macOS, or on a Linux distribution Pitboard’s repository does not cover, the pitboard cask installs the command line, with its man page and completions:
It and the pitboard-app cask both put pitboard on your PATH, so Homebrew installs only one of the two.

​
Install the command line on Windows

The app’s installer puts the command line on your PATH. For the command line alone, install it from its zip:
1

Download the zip

Under More options on Download Pitboard, download the ARM64 zip for a PC with an Arm processor, or the x64 one for any other.
2

Copy the command line out of it

The zip holds one folder, named like the zip. Copy pitboard.exe from it to a folder of its own, such as .local\bin in your user folder.You need not unblock it: pitboard.exe marked as downloaded from the internet ran from a terminal with no prompt, measured on 18 October 2026.
3

Add the folder to your Path

In Start, search for environment variables, then select Edit environment variables for your account. Under your user variables, select Path, then Edit. Select New, enter the folder, then select OK in both dialogs.In a terminal opened after that, check that it runs:
With cargo-binstall, name the release’s version, as Cargo says.

​
Install inside WSL

Claude Code and Codex installed inside WSL keep logins of their own, and Pitboard for Windows does not switch them. To switch them, install the command line inside WSL as on Linux, with the install script or Homebrew. There, pitboard doctor says on its WSL line what it switches. Where Codex’s home inside WSL is a folder on a Windows drive, such as /mnt/c/Users/me/.codex, Codex on Windows may use the same login. A switch on either side then changes it for both, so enrol and switch that Codex from one side only. Other ways to install covers Cargo, release files and building the app from source.

​
Update Pitboard

Updates lists the app’s update settings. brew upgrade --greedy also upgrades the pitboard-app cask. On macOS, if an update takes away a widget or control you placed, add it again, as See usage in a widget or from Shortcuts shows. Keep a command line installed apart from the app at the app’s version. An older one refuses a file the app wrote, with was written by a newer Pitboard. Next, add your accounts, or follow the Quickstart from its second step.