Your Windows PC can be the server

On this page
  1. Two things have to be true on the PC
  2. Why psmux and not tmux
  3. What happens when psmux is missing
  4. What works on a Windows session
  5. What is different from a Linux box
  6. Should you still use WSL2?

Yes. Agentmux connects to a native Windows PC over SSH, with no Linux layer inside it. Turn on the OpenSSH Server that ships with Windows 10 or 11, add that machine the way you add any other, and Agentmux gives you a PowerShell terminal, persistent sessions through psmux, and your coding agent.

The old answer was "put WSL2 in front of it", and the reason was one missing program. tmux has no Windows build, and tmux is the piece that keeps an agent alive when your phone drops. A program written for Windows covers that gap now, so WSL2 stopped being the only way in.

Two things have to be true on the PC

The first is an SSH door. Windows 10 and 11 both carry an OpenSSH Server as an optional feature, and you add it with one PowerShell command, run as administrator:

# PowerShell, as administrator
Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
Start-Service sshd
Set-Service -Name sshd -StartupType Automatic

The installer adds an inbound firewall rule named OpenSSH-Server-In-TCP. If the machine sits behind a stricter firewall than that, that rule is the first thing to look at. The second command starts the service now, the third keeps it running after a reboot, which matters more here than on a Mac: a Windows PC reboots for updates on its own schedule.

The second thing is the multiplexer. Agentmux asks the host what it is. A Windows host answers differently, and the app changes course: PowerShell for its own commands instead of sh -c, drive paths instead of slash paths, and psmux instead of tmux. It decides this by itself. There is no switch for you to find, and it does not care whether your login shell is PowerShell or cmd.exe.

Why psmux and not tmux

psmux is a separate program with a command line modelled on tmux: sessions, windows, panes, send-keys, capture-pane. It also installs a tmux.exe alias, so muscle memory survives. Agentmux looks for psmux, then pmux, then tmux.exe, and keeps whichever it finds, so a box that already has one of them is left alone.

It is not a port, and it does not pretend to be one. The app checks what the program actually answers instead of trusting a version string, and a capability it cannot prove goes unused. The differences below come out of those checks, not out of a compatibility list.

If you want the mechanism behind the requirement, what tmux is for is short and does not care which program fills the role: the connection dies, the shell receives SIGHUP, and an agent without a multiplexer dies with it.

What happens when psmux is missing

The app installs it. It tries winget install -e --id marlocarlo.psmux first, then Scoop, then cargo install psmux, whichever package manager is present, and reconnects. You are not typing anything on the phone.

A machine with none of those three is the one case where you have to intervene. The app says so plainly: Neither winget, scoop, nor cargo was found on the Windows server. Install psmux manually, then reconnect. A stripped Windows install or a server with winget removed lands here. Grab the binary, put it on PATH, reconnect.

Installing it that way leaves three names for the same program in one folder: psmux.exe, pmux.exe and tmux.exe. Type tmux on that machine and psmux is what runs, and psmux --version prints a tmux 3.4.0 line before its own version. Nothing is installed twice.

What works on a Windows session

  • Sessions are persistent. List them, create one detached, attach, rename, kill one, kill several at once. Ctrl-b d detaches you back to a PowerShell prompt and leaves the Agentmux tab open.
  • The agent runs in your project. Launch Claude Code, Codex, or your own command from a Windows path like C:\Users\you\src\app, spaces and all.
  • The app can still read the screen. Whether a pane is waiting for a permission prompt, working, or idle comes from the pane itself, and AI Permission Review can press the key on Windows instead of only naming the key it would press.
  • Both shells work. Windows PowerShell 5.1 and PowerShell 7, password or key authentication, drive letters, UNC paths, and folder names with spaces.

What is different from a Linux box

  • Files travel over SFTP. Browsing, editing and transfers use the SFTP subsystem rather than the shell, so if your OpenSSH install has it switched off, the file features say so instead of failing quietly. The terminal does not need it.
  • The file browser refuses two actions. Running a script, and Git operations. That is deliberate: a Windows host never answers them with a shell error you have to interpret.
  • No pane path. psmux has no pane_current_path, so the app cannot tell you which folder a pane is sitting in, and the line that reports the running program names PowerShell instead. That line also refreshes more slowly than on Linux.
  • Attachments land in the temp folder. A photo or file you attach goes to /tmp on a Linux or Mac host, and to the Windows temp folder on a Windows one. The path typed into the terminal is the real one either way.
  • Windows is the machine you connect into. There is no Agentmux that runs on Windows. If your Windows PC is the one you work at and the agent lives elsewhere, nothing here applies to you.

Should you still use WSL2?

One reason survives: you want a Linux userland, with apt, systemd, and slash-separated paths, rather than a Windows box that behaves like a server. Inside WSL2 every Linux step in this guide still applies.

The three traps are still there. WSL2 runs in a virtual machine behind NAT, so nothing outside the PC reaches the sshd inside it until you forward the port with netsh interface portproxy or turn on mirrored networking in .wslconfig. WSL shuts the distribution down seconds after its last process exits, so keeping it always on needs a scheduled task. systemd is off by default on older installs, and the wizard's service commands assume it exists.

So: pick WSL2 when you want Linux programs. Pick the native path when you want this PC to be your server, because there is no virtual machine in it to keep awake and no address that changes on reboot.

The door is open and the sessions survive. What is left is the address you type on the phone, and whether that address is safe to reach from the street.