aipat.ch· patching the gaps in AI
← Back to all projects
Coordination RDT · 04

roadTerm

roadTerm is my terminal. It is a nicer version of tmux with a bit of central coordination on top. Start a session at home, carry on from my phone on the train, pick it back up on my laptop when I arrive. Same session, wherever I am. Claude and the other tools I run stay where I left them.

Coordination In progress go · pty · websocket

About this project

roadTerm came out of wanting a better way to work on my servers. I live in terminals. Claude Code sessions, the various tools I run on the server, all day. I wanted somewhere better to keep them than raw tmux. Something I could reach for from any device and pick up exactly where I left off.

That is roadTerm. I start a session on my desktop at home, walk out, and if something comes to mind on the train I open roadTerm on my phone and carry on in the same session. When I open my laptop later, it is all there. Sessions, tabs, split panes, workspaces. A mix of tmux and Terminator with a bit of central coordination.

One thing it does that plain tmux doesn't is let bots on the server open and drive their own sessions. Doable spawns its task runners in roadTerm. A single Claude can launch a whole fleet of other Claudes through it, kick them off on their own work, and watch them go. Every command they run is visible in the UI, which means nothing the bots do is hidden from me.

On security: each user has their own server process, and the model is roughly shell access. If you could log in as that user and read their files, you could reach their roadTerm sessions. I only expose the backend over Tailscale, so it is reachable from machines I trust and nothing else. It works for me, but take a look at the model first if you want to try it yourself.

Screenshots

roadTerm supervised terminal
Web · desktop roadTerm supervised terminal

Details

RefRDT · 04
ZoneCoordination
StatusIn progress
Stackgo · pty · websocket
Source Not published