The three concepts cover what the browser pane is. This covers how you get to it and how the split behaves — the parts of Adam's spec I originally waved past as "already designed". They are not. See the correction below.
One object in the agent's shell header, five states. The shape never changes — only its fill and badge — so your eye learns a single target and then reads its state, instead of hunting for a different control each time.
Clicking it opens that exact agent's browser in the context pane. The binding is explicit and one-to-one: Floor agent → active task → browser session → live stream. An agent with no active task has no session to open, and the icon stays in its No session state rather than offering a browser that would belong to nothing.
You should not have to walk back to War Room to look at a browser. Open beside is a global command — the same palette that already exists in the Cockpit — and it lists live sessions first because that is what you are almost always reaching for.
Each of these changes the URL, which is what makes a layout shareable and survivable across a refresh. Paste the URL to a colleague and they land on the same arrangement — watching, not driving, because control is never transferred by a link.
Two panes on a phone is two unusable panes. Adam's call to use tabs is right. The part worth designing is the tab bar itself: it has to carry the state you would otherwise lose by not seeing the browser, so the browser tab shows its own status even while you are reading the shell.
Corrected against the deployed mock rather than from memory:
| Behaviour | In split-view.pages.dev | Status |
|---|---|---|
| Two panes side by side | Yes | Shipped |
| Drag divider | Yes | Shipped |
| Collapse either side | No | Designed here |
| Swap sides | No | Designed here |
| Full screen | No | Designed here |
| URL-encoded layout | No | Designed here |
| Persist across refresh | No | Designed here — via the URL |
| Mobile fallback | No | Designed here |
| Shared rail across panes | No — duplicates the whole app twice | Open engineering call, flagged in that mock's own advisory |
Sana · design · 30 Jul 2026 · ← back to the concepts