Prerequisites Before you begin, ensure you have:
Windows 10 or later (Windows Server 2019+ also supported)
Windows Terminal, CMD, or PowerShell
Downloaded the latest release binaries
Undying Terminal requires Windows 10+ for ConPTY support. Earlier Windows versions are not supported.
Installation
Download Binaries
Download the latest release from GitHub: # Download from releases page https: // github.com / Microck / UndyingTerminal / releases / latest
Extract the archive to a directory (e.g., C:\Program Files\UndyingTerminal)
Add to PATH (Optional)
Add the installation directory to your PATH for convenience: # PowerShell (Run as Administrator) $path = [ Environment ]::GetEnvironmentVariable( 'Path' , 'Machine' ) $newPath = " $path ;C:\Program Files\UndyingTerminal" [ Environment ]::SetEnvironmentVariable( 'Path' , $newPath , 'Machine' )
Verify Installation
Verify all three executables are present: ls C:\Program Files\UndyingTerminal\
You should see:
undying-terminal-server.exeundying-terminal-terminal.exeundying-terminal.exe Basic Usage 1. Start the Server Open a terminal and start the server:
. / undying-terminal-server.exe
By default, the server listens on port 2022. You can change this in the configuration file.
Expected output:
[INFO] Server listening on 0.0.0.0:2022 [INFO] Named pipe server started: \\.\pipe\undying-terminal
2. Start a Terminal In a new terminal window , start a terminal session:
echo "XXX/ignored" | . / undying-terminal-terminal.exe
The echo "XXX/ignored" provides a dummy stdin input. The terminal will print its client ID and passkey on first run - save these for the next step!
Expected output:
[TERMINAL] Client ID: abc123def456 [TERMINAL] Passkey: 1234567890abcdef [TERMINAL] Ready for connection
3. Connect the Client In a third terminal window , connect to the session:
. / undying-terminal.exe ` -- connect 127.0 . 0.1 2022 abc123def456 ` -- key 1234567890abcdef ` -- noexit
Windows Terminal / PowerShell
CMD
. / undying-terminal.exe ` -- connect 127.0 . 0.1 2022 < CLIENT_ID > ` -- key < PASSKEY > ` -- noexit
You’re now connected! Try typing commands - they’ll execute in the remote terminal session.
Testing Session Persistence Let’s verify that your session survives disconnects:
Start a Long-Running Process
In your connected terminal, start something that takes time:
Kill the Client
Close the client terminal window (or press Ctrl+C)
Reconnect
In a new terminal, reconnect using the same command: . / undying-terminal.exe ` -- connect 127.0 . 0.1 2022 abc123def456 ` -- key 1234567890abcdef ` -- noexit
Verify Recovery
You should see:
The ping is still running
Recent output is replayed (catchup)
New output continues streaming
Success! Your session survived the disconnect and recovered seamlessly.
One-Shot Commands Execute a single command without interactive mode:
# Note: include `r`n for cmd.exe newline . / undying-terminal.exe ` -- connect 127.0 . 0.1 2022 < CLIENT_ID > ` -- key < PASSKEY > ` - c "echo Hello World `r`n "
The client will:
Connect to the session
Send the command
Wait for output
Exit when idle
SSH Bootstrap (Remote Servers) Connect to a remote server and start a persistent session:
. / undying-terminal.exe -- ssh user @remote -server.com - l username
This will:
SSH to the remote server
Start undying-terminal-terminal remotely
Extract the client ID and passkey
Connect directly via TCP
Keep the session alive even if SSH drops
SSH bootstrap is perfect for remote development servers. After initial setup, your session survives network changes!
Tmux Integration (v1.1.0+) For servers with tmux installed, auto-attach to a tmux session:
. / undying-terminal.exe -- ssh user @remote -server.com - l username -- tmux -- tmux - session myproject
This combines Undying Terminal’s network resilience with tmux’s session persistence.
Predictive Echo (v1.1.0+) For high-latency connections, enable local echo:
. / undying-terminal.exe -- ssh user @remote -server.com - l username -- predictive - echo
Characters appear instantly while typing, improving responsiveness on slow networks.
Configuration File (Optional) Create a config file for persistent settings:
ut.cfg
Create Config Directory
# %PROGRAMDATA%\UndyingTerminal\ut.cfg port =2022 bind_ip =0.0.0.0 verbose =false shared_key_hex =<your-hex-key>
Built-in UI (v1.1.0+) For managing multiple sessions, use the built-in UI:
. / undying-terminal.exe -- ui
Example workflow: ut-ui> add dev localhost 2022 <client_id> <passkey> ut-ui> add prod prod-server.com 2022 <client_id> <passkey> ut-ui> start dev ut-ui> list - dev host=localhost port=2022 running=yes - prod host=prod-server.com port=2022 running=no ut-ui> quit
The UI makes it easy to manage multiple environments without remembering complex commands.
Learn More Full guide to the built-in UI
Next Steps Troubleshooting
Server won't start - port already in use
Check if port 2022 is already in use: netstat - ano | findstr : 2022
Either:
Kill the process using the port
Change the port in ut.cfg
Use --port flag: ./undying-terminal-server.exe --port 2023
Client can't connect - connection refused
Verify:
Server is running (netstat -ano | findstr :2022)
Firewall isn’t blocking port 2022
Client ID and passkey match terminal output
Enable verbose logging: $ env: UT_DEBUG_HANDSHAKE = 1 . / undying-terminal.exe -- connect ...
Named pipe errors on multi-server setup
If running multiple servers on one machine (dev), set unique pipe names: # Server 1 $ env: UT_PIPE_NAME = "\\\\.\\pipe\\undying-terminal-2022" . / undying-terminal-server.exe -- port 2022 # Server 2 $ env: UT_PIPE_NAME = "\\\\.\\pipe\\undying-terminal-2023" . / undying-terminal-server.exe -- port 2023
Summary You’ve learned how to:
Install and run all three components
Create and connect to persistent sessions
Test session recovery
Execute one-shot commands
Use SSH bootstrap for remote servers
For production use, consider running the server as a Windows service and enabling encryption via shared_key_hex in the config file.
