Hanzo Tabs
Keep tabs on your agents.
Your coding agents work in shells on real machines. Tabs puts every one of those shells in front of you — split, tiled, and reachable from anywhere you can open a browser.
Link a machine, and it appears here.
hanzo linkRun it on a laptop, a workstation, a GPU box — anything with a shell. The machine keeps the connection; nothing is exposed to the network it sits on.
- No server to run
- Tabs has no backend. `hanzo link` on a machine publishes a terminal over a zero-trust tunnel, and Tabs frames it. Nothing to deploy, nothing to keep up, no port to open.
- Many shells, one link
- A shell is a URL. One link serves as many independent tmux sessions as you ask for, so a build can run in one pane while you work in another — on the same box or a different one.
- Your terminal, not a viewer
- A real xterm.js terminal with 10k lines of scrollback, true colour and a cursor that blinks. Type in it, page through it, resize it.
- Closing a pane loses nothing
- Every shell is a tmux session that keeps running when the browser goes away. Reopen it by name and the scrollback is exactly where you left it.
- Works on a phone
- Splits become swipeable pages instead of unreadable slivers, and a key row gives you Esc, Ctrl, Tab and arrows — the keys a soft keyboard does not have.
- Open source, MIT
- The layout engine, the terminal client and this site. Fork it, host it, or run it against your own machines.