Panes, tabs, and the drawer
The workspace is a mixed tree of panes, tabs, and splits, with a utility drawer along the right edge. Everything in it acts on one of three things: the focused session, the active Project, or the whole application.
Panes and splits
| Chord | Action |
|---|---|
| Ctrl+Alt+H | Split the focused pane right |
| Ctrl+Alt+V | Split the focused pane below |
| Ctrl+Alt+Z | Zoom the focused pane, and unzoom it |
| Ctrl+Alt+D | Detach the focused pane |
| Ctrl+Alt+Left / Right | Focus the previous or next pane |
| Ctrl+Tab / Ctrl+Shift+Tab | Focus the next or previous workspace tab |
Split geometry is durable per-Project state, so a layout you built survives a reload and a restart. Panes can be dragged and dropped, stacked into tabs, and dissolved back out.
A pane is not only a terminal. Notes, files, previews, and static documents all open into one, which is what makes it worth building a layout at all.
The utility drawer
On the desktop it is an in-flow split beside the workspace with an always-visible launcher rail, so it never covers what you are working on. On a phone it is an overlay entering from the right edge. Same tabs, same order.
| Tab | Acts on | What it is for |
|---|---|---|
| Actions | the focused session | Rail keys, prompt templates, discovered agent skills, and the clipboard history. Everything that puts text into the terminal. |
| Queue | the focused session | Stage ordered messages against a mid-turn conversation, and decide when they go. |
| Transcript | the focused session | The conversation, read from the harness's own transcript. |
| Activity | the focused session | What the run did: the scan timeline, the detectors' findings, and the change map of files it actually wrote. |
| Agent | the focused session | What this agent is running with: its tools, its policies, and its instruction files. |
| Files | the Project | A bounded file tree with editors. Picking a file opens it in a pane. |
| Notes | the Project | The note collection and the editor itself, so you can read or add to a note without losing the terminal on a phone. |
| Git | the Project | Status, comparison, diff review, the worktree map, provenance, and the landing strip. |
| Processes | the focused session | What this session started, and what each one is serving. Hidden by default. |
| Schedule | the Project | What this Project will start later, with its own fleet-wide scope. |
| Alerts | the application | The ranked attention inbox across every Project. The one application-wide fleet view with a permanent tab. |
Tabs can be hidden, reordered, and drawn as icons or titles in Settings, Appearance. A surface folded into another tab keeps its own command-palette entry and its own voice phrase, so nothing becomes reachable only by remembering where it went.
Watch here, act there
Two pairs of surfaces look like duplicates and are not, for the same reason each time. The Queue tab is beside the terminal because deciding whether to send a message is a judgement about the agent's live state, and that state is only legible in the terminal; the Fleet Queue is a modal because it has no send button and nothing in it needs a terminal beside it. The Processes tab answers "what is this session running" beside the pane; the Resources dialog covers the terminal and answers the fleet-wide version.
On a phone
The phone renders a single-pane projection of the same workspace tree rather than a second layout, so a session you split on the desktop is still there and still in order. Navigation is a top bar with horizontal swipe between Projects, an overlay for the sidebar, and the drawer from the right edge.
A touch key rail carries the keys a phone keyboard does not have, and a two-finger swipe down enters a read and select mode that keeps the on-screen keyboard out of the way.
The command palette reaches everything
Ctrl+Alt+P. Every command in the application is in it, including the ones with no default chord, and every one of them is bindable to a chord or a mobile gesture. The keyboard reference has the defaults.