A terminal session that survives disconnecting
The single most useful thing about a machine that stays on is a terminal that stays open. This is a persistent Zellij session, opened from the dashboard, with a tab for whichever coding CLI you want to run.
It starts by default, because a machine whose terminal has to be started is a machine that has already lost the session you wanted.
How it arrives
- On the machine
- Installed as part of the build
- At boot
- Starts when you start it, and holds nothing until then
- Reached at
- /zellij/ on your machine's own HTTPS name
- Memory while running
- about 2 GB
We did not write Terminal+. It is zellij-org/zellij — the terminal workspace the persistent session runs in. We install it on every machine and put it behind the login.
Disconnecting is not stopping
The machine is a real VM that keeps running when you close the tab. A process you start does not stop because your laptop slept, your train went into a tunnel, or you switched to your phone.
Reopening the dashboard reattaches to the same session — same tabs, same running processes, same scrollback. This is what makes it reasonable to start a long agent run and walk away.
A tab per agent
Claude Code, Codex, OpenCode, Gemini and Kimi each get a tab from the dashboard. They are all on one machine looking at one set of files, so putting two of them on the same problem is a keystroke.
Questions
- What happens to a running command if I close the tab?
- It keeps running. The session lives on the machine; the browser is only attached to it.
- Can I reattach from a different device?
- Yes. Sign in from any browser and open the same session.
Once you have one
It comes with the machine
Every tool on this site is installed on every machine. You are choosing a size, not a bundle.