Skip to main content

UI Layout

How the Daintree window is laid out: the toolbar and its launcher, the sidebar and its footer, the panel grid, the dock, the portal, and multiple windows.

Updated
Reviewed

Overview

A Daintree window is divided into five areas. Each has a distinct job; several can be resized, hidden, or replaced by a project-specific surface.

  • Toolbar: the top strip. Fixed anchors at the edges, the project switcher pill in the middle, and the launcher plus whatever you have pinned in between. Once you have added a remote host, the host chip beside the pill says which machine the window is on.
  • Sidebar: the left column, listing every worktree in the current project, with an activity readout and Run command in its footer.
  • Panel grid: the center. Everything you are actually working in lives here. See Terminals & Panels.
  • Dock: the bottom bar. Its launcher +, the panels you have moved out of the grid (still running), and the status containers that collect waiting, errored, backgrounded and trashed panels.
  • Portal: an optional right-hand browser panel. See Portal Browser.
The toolbar, the worktree sidebar, the panel grid, and the dock along the bottom.

The worktree sidebar runs down the left edge. Toggle it with Command-B Control-B Control-B , drag its edge to resize it (350px by default), and the width persists across sessions. Pinned worktrees sit at the top, and the footer sits below the list.

In a narrow window, the sidebar can temporarily shrink to leave room for the grid without changing your saved width. Widen the window and that width comes back. This supports the smaller windows used by Linux tiling window managers; see the Linux release changes.

What a card shows, how the list is sorted and filtered, and its full keyboard model are documented at Worktree Cards, which owns that surface.

Hiding the sidebar from the keyboard

A whole region of the window vanishing is alarming when nothing connects it to what you just pressed. So when Command-B Control-B Control-B hides the sidebar, Daintree raises a notice that names the combination that did it ("Sidebar hidden. Command-B Control-B Control-B toggles the sidebar") with an Undo button and a 30-second window to use it.

The notice fires in one direction only. Bringing the sidebar back is self-evidently what happened, so it says nothing. It fires only for a bare keypress: a menu item, a palette entry or a toolbar click already named itself at the moment you clicked. And it retires after three showings for a given binding, because by then it is a habit rather than a slip. Pressing Undo resets that count: reaching for Undo is the evidence the keypress was a slip.

The binding is read live, so if you have rebound the sidebar toggle the notice names your combination, not the default.

The bottom of the sidebar is one row. On the left, an activity readout says what Daintree is doing across every project: a filled dot while agents are working and a hollow one at rest, beside a count such as 2 projects active, or Working / Idle when none is counted. On the right, Run command opens QuickRun above the row; whether it is open is remembered per project. A warning triangle appears beside the readout when Daintree's own memory use is high.

Occasional rows sit above it. When the machine itself is short of memory, a quiet line states what was measured and offers Memory actions; see The memory notice. A project whose own plugins need attention (blocked, waiting to be enabled, unreadable or failed) gets a row that leads back to them.

Click the readout for the resource popover:

  • Memory: Daintree's own memory use, terminal memory by project, and what the system has available. Each process is counted in full, so memory two processes share is counted twice and the totals run high.
  • Running processes: opens the dialog described below.
  • A keep-awake line (Keeping this machine awake or Not keeping this machine awake) that opens its setting.
  • A diagnostics section with process and heap readings.

Running processes

The Running processes dialog lists every terminal and plugin process across all projects and windows, including terminals whose panel isn't on screen, grouped by project. Each terminal shows its PID, its member processes, and sampled CPU and approximate memory. Terminals and dev previews can be killed from here after a confirmation; a dev preview is stopped through its own session, so a pending restart is cancelled with it.

Processes that outlived the terminal that started them (a backgrounded job, a server an agent left running) are tracked and listed under From closed terminals, where you can kill them too. Plugin workers and their child processes are listed under Plugins.

Check processes across projects from one dialog

Panel grid

The panel grid holds every open panel for the selected worktree. Its layout strategies, scrolling behavior, tabs, maximize, focus mode and the empty-grid launcher all live on Terminals & Panels, which is the canonical page for the panel model.

One grid behavior belongs here because it is a launcher surface: right-clicking empty grid space opens the full launcher inventory inline (Agents, the panel kinds under Open in grid, and Recipes), then a Grid layout submenu (Automatic, Fixed columns, Fixed rows), then Panel grid settings…. It is the same inventory the toolbar + shows, rendered as menu items.

A project plugin can add a home surface to an empty canvas, giving the project its own dashboard or starting workflow. It does not replace an active panel grid. See Project-level plugins.

Portal

The Portal is a browser panel pinned to the right side of the window, for keeping a web chat, a set of docs or a dashboard next to your agents. Toggle it with Command-\ Control-\ Control-\ . It has a launchpad of detected AI chat services and its own tabs. See Portal Browser.

Palettes and menus

Every keyboard-driven overlay in Daintree (the action palette, the quick switcher, the launcher, the project switcher and every other one) runs on one shared surface with one grouped keyboard model. Right-click menus on panels, worktree cards and file rows are the pointer-driven half of the same job. Both have their own page: Palettes & Menus.

Status banners

Transient status messages across the workspace share one banner chrome. A snapshot restore notice, a degraded file watcher, a settings-sync conflict, a plugin that failed to load: same layout every time: a severity icon, a short title, a description line, and any actions inline on the right. The chrome is identical across the workspace, a panel and the settings dialog, so a banner means the same thing wherever it appears.

Severities are the standard set: error, warning, info, success and neutral. The close affordance is always in the same place, and a banner with an attached action puts the label inline rather than behind a menu. On Windows, the native caption strip tints to match whichever banner currently occupies the top band, so the window chrome and the banner read as one surface.

Toolbar, dock and windows

The chrome above and below the grid, plus what happens when you open a second window, is documented in one place: Toolbar, Dock and Windows. That covers toolbar customization and its groups, the launcher, overflow behavior, docking and undocking panels, and multi-window rules.