Works with any program
Shells, editors, htop, coding agents. Colors, full-screen apps, and scrollback render as they do locally.
RETURN TO YOUR TERMINAL
Securely reach a terminal session running on your machine from any device. Work locally as usual, then continue from the browser when you need to.
Get started❯ reterm npm run dev > dev > vite VITE v8.0.16 ready in 220 ms ➜ Local: http://localhost:5173/ ➜ Network: use --host to expose ➜ press h + enter to show help
ReTerm
ReTerm
1 session
1 remote
> dev
> vite
VITE v8.0.16 ready in 220 ms
➜ Local: http://localhost:5173/
➜ Network: use --host to expose
➜ press h + enter to show help
One running process. Local when you’re there, available in the browser when you’re not.
Shells, editors, htop, coding agents. Colors, full-screen apps, and scrollback render as they do locally.
Running Claude Code, Codex, or opencode? A dot on each session shows working, needs you, or idle.
Send a link, approve who asks to watch, remove them any time. Viewers can never type.
Get started
One small binary, no installer, no dependencies. Download it and wrap your first command.
1Install with one command:
curl -fsSL https://reterm.dev/install.sh | sh
Or download the binary directly:
1Install with one command:
curl -fsSL https://reterm.dev/install.sh | sh
Or download the binary directly:
1Install with one command:
irm https://reterm.dev/install.ps1 | iex
Or download the binary directly:
2Sign in once:
reterm --login
Opens your browser to approve the device, then caches the credential.
3Wrap any command:
reterm claude
Runs your command locally and makes its live session available in the browser.
Next: take control from the browser, hand it back, and share a session. Read the guide →
Control without surprises
Remote control is an explicit state, not a second stream of competing input. If the browser or relay disconnects, input returns to the local terminal and the process keeps running.
Security
Sessions belong to the signed-in user. The relay routes live traffic; it does not become the machine running your tools.
Your account gates the session list and browser attachment. Users see only their own sessions.
Password-protected sessions keep terminal content and metadata encrypted through the relay.
Sessions exist while the wrapped process is connected. The live registry is not persisted.
Contact
Send a message and we'll get back to you. No account needed.