Typed in a terminal, devpit shows a menu instead of opening the window straight away: the installer's banner, then seven items.
| Item | Subcommand | What it does |
|---|---|---|
| Open devpit | devpit open |
starts the app apart from the terminal, so closing the terminal leaves it open. One already running comes forward |
| Status | devpit status |
the version, the sessions running and those waiting on you, the free space on the disk devpit's folder is on, and the load against the number of CPUs |
| Pair a device | devpit pair |
a pairing code for the Remote, a QR code of the pairing link, and the link. The device still waits for you to allow it on devpit's screen |
| Web version | devpit web |
says it is coming with Remote |
| Update | devpit update |
runs the installer's own command in the same terminal. See Staying up to date |
| Diagnostics | devpit diagnostics |
the checks below, each failing one with its fix |
| Quit | leaves the menu |
The arrow keys, or j and k, move; Enter picks; a number picks its item at once; q, Esc, Ctrl-C or Ctrl-D quit. An item prints under its name and the menu comes back below it. Open devpit and Update hand over and end the menu.
In scripts
A subcommand runs one item and prints plain lines, with or without a terminal, so scripts and launchers keep working. devpit diagnostics exits 1 when a check fails. Started with no terminal at all, from a launcher, devpit opens the app as it always did, and devpit menu shows the menu on purpose.
Status and Pair a device ask the running app. With devpit closed they say so, and pairing with Remote off says to turn it on in Settings → Remote.
The checks
- devpit is open;
- the
claudeCLI is installed; - tmux is installed (not on Windows);
- the disk has 5 GB free;
- the load is under the number of CPUs.
A check this system cannot make, such as the disk or the load on Windows, does not fail. Settings → Diagnostics shows the same checks.