Tabs and splits

Every session you open is a tab. Every tab holds a pane tree — one terminal, or many, split vertically and horizontally.

┌ my-app ●busy ┬ tests ○idle ┬ notes ────────────────┐
├──────────────┴─────────────┴───────────────────────┤
│                        │                           │
│   claude (my-app)      │   $ cargo test            │
│                        │                           │
│                        ├───────────────────────────┤
│                        │                           │
│                        │   $ git log --oneline     │
│                        │                           │
└────────────────────────┴───────────────────────────┘
   mod+D splits vertically · mod+Shift+D horizontally
        (mod = Cmd on macOS, Ctrl on Windows and Linux)

Tabs

Jump-to-tab is matched by physical key position, not by the character the key produces. On AZERTY and QWERTZ, where the number row produces &, é, … without Shift, Cmd/Ctrl+1 still lands on tab 1.

Each tab carries its own activity dot (see Status and attention), a title derived from its session, and a × to close it. Hovering a tab shows the session’s fuller description — the same card the sidebar shows.

Tabs reorder by drag-and-drop. Press a tab and drag it onto another slot: the carried tab fades, the drop slot is outlined, and the reorder commits on release. A plain click still just activates the tab. The order lives in the pure workspace model — the tab strip holds only transient pointer state, so there is no second, rival tab tree to drift out of sync.

Splits

A split opens a fresh shell beside the focused pane. Directional focus walks the pane tree geometrically — Cmd/Ctrl+Shift+→ goes to the pane on the right, whatever the nesting.

Closing the last pane in a tab closes the tab.

Drag-resize is not shipped yet. Panes divide their space evenly; the remaining piece of F-terminal-split is a draggable divider. Two extra focus actions, focus-next and focus-prev, exist in the keymap with no default chord — bind them yourself if you prefer cycling to directional movement (settings.json).

Closing, and what asks first

Closing a tab, and quitting the app, are each governed by their own confirmation policy — alwaysConfirm, confirmWhenActive (the default), or noConfirmation. Under the default, a tab whose session is mid-command asks before closing; an idle one closes silently. Quitting names how many sessions will be force-stopped.

A pane whose shell exits cleanly closes itself; one whose shell exited with a failure stays on screen so you can read what happened.