Panel
The Panel is how you drive work on paired machines from a browser. It holds no projects, sessions, or files of its own — everything live arrives over the panel-link; first paint is server-rendered, then the tab stays current.
A Panel that knows no Cores opens in the first-run wizard — install a Core, pair it, and the app unlocks. After that you always start in Fleet: every Core's sessions in one list. Click a Core to enter it. The shell has no Core switcher — to work on a different machine, go back to Fleet and pick another.
Inside a Core the surface is the same every time: project rail, session grid, then the live terminal. Sessions split into needs-input, running, and finished, so a machine that is waiting on you is visible without opening it.
flowchart LR
W[First-run wizard] -->|pair a Core| F[Fleet]
F --> C[Pick a Core]
C --> P[Project rail]
P --> G[Session grid]
G --> T[Terminal]
In this section
- First-Run Wizard — what a Panel with zero Cores shows, and why there is no way past it.
- Fleet — live fan-out across Cores.
- Projects — folders on the Core; unlink never deletes files.
- Sessions — real PTYs, one writer, others read.
See also
- Panel Installation — deploy, configure, back up.
- Panel Pairing
- How it works