Demo

There is no public demo, and there is a reason.

A shared instance would be a machine strangers could open a terminal on. What follows is what each surface actually looks like; installing it takes about fifteen minutes if you want the real one.


01 · The fleet

Every machine, and what is up.

Ports are checked on every load — batched through the agent when the machine is online, and an 800 ms TCP probe when it is not. The arrow direction is the point: each machine reached out to the server, not the other way round.


dd-a41f · tmux
$ npm run build ▲ Next.js 15.0.0 Creating an optimized production build ... ✓ Compiled successfully # laptop closed — session keeps running # reattached from the phone 40 minutes later $ _
02 · A terminal

Real tmux, not a web shell.

Close the tab and the build carries on. Reattach from another browser or the phone and you are in the same session. Open your native terminal and you join that one too.


03 · An AI session

Waiting on you, or working.

Read from the transcript the CLI already writes, so it does not break when the CLI redraws its interface. A push fires on the working → waiting transition, with a two-minute cooldown.

claude · mbp-14 · ~/www/api
you the migration fails on a fresh database claude The column is added by a script that is not in the ordered list, so it never runs. Add it and redeploy — shall I? ▸ waiting for your reply · 2m

tunnel
local http://localhost:3000 public https://dialout.dev/ws/tunnel/mbp-14/3000/ rewritten in the response: /_next/… /api/… in html, js, css fetch · XMLHttpRequest · pushState anchor clicks · Navigation API Location headers on redirects
04 · A tunnel

Send the URL, not a deploy.

The response is rewritten so the app survives being served under a path prefix. That is the difference between a client seeing your branch and a client seeing a page that loads its shell and stops.


The real one runs on your server.