psmux provides persistent terminal sessions for Windows PowerShell. It is useful for long-running tasks and reconnecting after a disconnect. Unlike tmux on Linux and macOS, psmux runs in the native Windows environment.
psmux is for native Windows PowerShell, not WSL. It is a limited compatibility feature; use tmux or herdr inside WSL.
Requirements
- Native Windows OpenSSH Server is enabled. Follow the Microsoft OpenSSH for Windows guide.
- Redock connects to the Host with SSH.
- The remote account can run
psmux. - PowerShell 7 is recommended.
Install psmux
With winget:
winget install psmux
With Scoop:
scoop bucket add psmux https://github.com/psmux/scoop-psmux
scoop install psmux
Verify the installation with the same account used over SSH:
psmux --version
Enable It in Redock
- Edit the Host.
- Confirm that Connection Mode is SSH.
- Select psmux under Session Persistence.
- Save and reconnect.
tmux sessions inside WSL and native Windows psmux sessions are separate and will not appear together.
Common Issues
- psmux not found: Add
psmuxto the systemPATH, reconnect SSH, and restart OpenSSH Server if needed. - Session cannot be restored: Confirm that the Host uses SSH, psmux is installed correctly, and Redock connects as the same Windows user.
After setup, save common PowerShell commands as Actions and use Projects for Windows development environments.