devpit

Windows

A native installer with psmux inside it, or the Linux build inside WSL 2.

devpit runs on Windows two ways: a native installer, whose terminals run on psmux, or the Linux build inside WSL 2. Both keep your terminals in a tmux of their own, which is how they outlive the window.

The installer

Download the installer — always the newest devpit_<version>_x64-setup.exe — and run it. Every version is also on the releases page.

  • It is an NSIS installer that installs for your user only, so it needs no administrator rights.
  • It carries psmux, a tmux of Windows' own, which devpit's terminals run on there. Nothing else to install for the terminals.
  • It adds devpit to the Start menu, and removes cleanly from Settings → Apps.
  • It needs Claude Code on PATH (claude), and WebView2, which the installer fetches if Windows lacks it.

The install line does not install on Windows. Run there, it stops and points at the installer.

SmartScreen

The installer is not signed with a code-signing certificate, so SmartScreen stops it the first time with "Windows protected your PC". That is the missing certificate talking, not the file. Check it against the release's SHA256SUMS first. In PowerShell, this prints the hash that should match the first half of the file's line there:

(Get-FileHash .\devpit_<version>_x64-setup.exe).Hash.ToLower()

Then More info → Run anyway.

What is different on Windows

  • Terminals run PowerShell, with devpit's prompt marks, and find what a new Windows Terminal tab finds. A new terminal opens in its project's folder, not your home.
  • Programs are found under their .exe or .cmd, on the PATH Windows keeps for you, so the chat finds your Claude Code profiles. The agents offered are the ones actually installed.
  • Nothing devpit starts flashes a console window.
  • Closing the last terminal ends psmux, and installing over devpit or removing it ends it first.

Updates close your terminals

devpit updates itself on Windows as it does elsewhere: it downloads the installer, checks its signature, runs it and reopens. But your terminals close. Windows will not replace a program that is running, so the installer ends the psmux inside devpit first. The update card says so before you restart, so you can finish what is running. See Staying up to date.

Removing it

Settings → Apps → devpit → Uninstall. Your work stays in %USERPROFILE%\.devpit; delete that folder too to erase everything.

Or inside WSL

The Linux build runs in WSL 2, and its window is drawn by WSLg on the Windows desktop. The terminals are tmux sessions inside WSL and outlive the window there, updates included.

  1. Windows 11, or Windows 10 21H2 or later, with WSL 2 and a Linux distribution: wsl --install in PowerShell, then restart.

  2. In the distribution's shell: sudo apt install tmux wslu, and Claude Code as its own install page says.

  3. The same line as on Linux, inside WSL:

    curl -fsSL https://devpit.app/install.sh | sh
    
  4. Keep projects in the Linux file system (~/…), not under /mnt/c: git and the file watchers are many times slower across that border.

wslu is what opens a link in the Windows browser. Two things do not reach across: signed-in sessions brought from a Windows browser (see Signing in), and files dropped from Explorer.

Which to choose

Installer WSL 2
Terminals PowerShell, on psmux your Linux shell, on tmux
An update closes the terminals the terminals keep running
Projects on the Windows disk in the Linux file system
Signing not code-signed; SmartScreen asks once checked like any Linux install

If your work already lives in WSL, the Linux build there is the closer fit, and an update never interrupts a terminal.