Toolbar, Dock and Windows
The application chrome around the panel grid: toolbar customization and groups, the searchable launcher, overflow behavior, the dock and how panels move in and out of it, and what happens when you open a second window.
Toolbar
The toolbar has two fixed anchors that never move and never overflow: the sidebar toggle on the far left, and the assistant toggle on the far right. The project switcher pill sits in the center. Everything else is a left group and a right group filling the space between, and both groups are yours to arrange.
On Windows and Linux an Application menu button sits before the sidebar toggle. It pops up the app's real menu (File, Edit, View, Terminal, Window, Help), which on Windows has no title bar to live in. It is fixed chrome too: it can't be hidden or overflowed, because it is the way back to every menu-only command. macOS keeps its system menu bar instead.
| Anchor | Shortcut | What it does |
|---|---|---|
| Sidebar toggle | Command-B Control-B Control-B | Shows or hides the worktree sidebar. |
| Assistant toggle | Command-L Control-L Control-L | Opens the Daintree Assistant. |
Focus Mode is a separate action on Command-K, then Command-F Control-K, then Control-F Control-K, then Control-F . It hides the sidebar and the assistant, where Command-B Control-B Control-B only hides the sidebar.
The launcher
The launcher is the + button at the head of the left group, and it is the one searchable surface for starting anything. It replaced the separate agent tray and panel tray that used to live on the toolbar, along with the dock's own +. The same component serves both positions with the same inventory: only the trigger, the direction it opens, and where a new panel lands differ.
Open it and you get a search field ("Search agents, panels, and recipes"). With nothing typed, the inventory is laid out in two columns, cut so they end level, with a footer underneath; on a narrow window the columns fold into one. Arrow keys read down the first column, then the second, then along the footer.
| Heading | What it holds |
|---|---|
| Agents | One list for every agent. Up to three you launched most recently come first, marked Recent; the rest follow with the ones pinned to the toolbar first. Pinning is row state, a filled pin, rather than a heading of its own. Agents that are installed but not ready to launch follow, marked Setup. With no agent CLI installed at all, the list offers every built-in agent with a route to setup, followed by a Set up agents row. See Agents. |
| Open in dock / Open in grid | Panel kinds, headed by where selecting one actually lands the panel. From the toolbar everything opens in the grid; from the dock, kinds the dock can't hold are listed under Open in grid rather than hidden. Plugin-registered kinds carry a Plugin or Project plugin label. |
| Recipes | Saved recipes with their scope, or a Create a recipe row when you have none. |
| More | The footer: Manage agents and Customize toolbar…. |
Type a query and the columns collapse into a single ranked Search results list, capped at 30, where each row also names its type (Agent, Panel or Recipe). Typing a preset's name finds the agent that owns it. With an empty query the browse layout renders in full: the point of browsing is to see the whole inventory.
Four things happen on the rows themselves:
- Alt+P pins the selected row to the toolbar, or unpins it if it is already there. It has to be a modified key because the field is a type-ahead search. Agents, panels, recipes, and individual presets can each get their own toolbar button; unpinning puts it back to being "listed in the launcher". The pin control on each row does the same with the pointer.
- A keyboard button records a launch shortcut inline on an agent row, or press F2 on the highlighted agent. Press the combination you want and that agent's launch action is bound to it without a trip to Settings.
- An agent with something running shows a state pip in its own state color, so you can see at a glance whether launching would be your first Codex session or your fourth.
- A newly detected agent wears a small blue dot beside its name, and the toolbar's + carries the same dot. Install a CLI and the launcher tells you it found it, rather than waiting for you to go looking.
An agent with presets expands with ArrowRight (at the end of the query) and collapses with ArrowLeft, or click the chevron at the start of its row. Preset rows appear as siblings under the agent, grouped by where they came from (CCR routes, project shared, custom) with a Default choice that launches the agent with no preset at all.
On a fresh profile the toolbar ships with just Launcher, Terminal and Browse files on the left. Agent buttons are no longer defaults: an unpinned agent means "listed in the launcher", not "hidden". A profile created before this change keeps every agent button it already had, which is why two machines can show different toolbars.
What else is on the toolbar
The rest of the row is a per-profile inventory rather than a fixed set, so this is what each button is rather than a claim about what you will see:
| Button | What it does | When it renders |
|---|---|---|
| Terminal | Opens a new terminal panel. | Default on the left |
| Browse files | Opens the File Browser for the active worktree, or for the project or scratch root when no worktree is selected (Option-Command-F Control-Alt-F Control-Alt-Shift-F ). | Default on the left; unavailable with no workspace open |
| Browser | Opens a browser panel. | Only when you pin it |
| Dev preview | Starts the dev server and opens a Dev Preview. | Only when you pin it; a placeholder until a project is open |
| Agent buttons | One-click launch for a specific agent. | Only when pinned and the agent is available |
| Plugin tray | A dropdown collecting every plugin's toolbar contributions, grouped by plugin. | Only when a plugin contributes a button |
| Voice recording | The dictation indicator. See Voice Input. | Occupies a fixed slot; visible only while recording |
| Repository activity | Commits, issues and pull requests for the project. See Code Forge. | Only for a git-backed project |
| Links | Opens the links launcher: project links, links your manifests declare, your own links, the active worktree's pull request, checks and deployments, and dev servers. | Default on the right, but only while it has something to show |
| Canopy | Opens Canopy, an inbox of every agent across your projects, ordered by what needs you (Command-E Control-Shift-O Control-Shift-O ). Canopy is on by default and reads your agents' terminals on your machine, with a model that ships with Daintree. A badge counts the urgent asks. | Default on the right, unless you hide Canopy |
| Notifications | Notification history dropdown. | Only when notifications are enabled |
| Copy context | Opens the copy-context recents dropdown. See CopyTree. | Always; unavailable with no project or scratch open |
| Command palette | Opens the action palette (Shift-Command-P Control-Shift-P Control-Shift-P ). | Always |
| Resume session | Browses closed agent sessions. See Session Management. | Always |
| Settings | Opens Settings (Command-, Control-, Control-, ). | Always |
| Problems | Opens the Problems panel. | With Developer Tools enabled, or on its own while file watching is unreliable |
Repository activity renders as a three-segment pill (commits, issues, pull requests) when a forge provider is resolved, and collapses to commits only when there is none, since a commit count is local git data and needs no provider. A workspace with no repository gets a same-sized placeholder rather than an empty gap, which also keeps its polling from ever starting.
Copy context is a dropdown, not a one-shot button: Copy full context on top, your recent copies underneath (each with its size and when it last ran), and Context settings. In a scratch workspace or a folder opened without git it copies the workspace root. When a copy finishes, the button's own tooltip reports it in place; if the button can't be seen, a notification takes its place. CopyTree covers what the recents list keeps and how a copy is shaped.
Groups and dividers
Every toolbar button declares a group (launcher, agents, panels, utilities) and buttons are partitioned into that order at render time, keeping your relative order inside each group. A divider is drawn wherever the group changes, so on a normal layout the left side reads launcher, divider, agents, divider, panels.
Dividers count only visible buttons. A button evicted into the overflow leaves no divider behind, and when a whole group overflows the boundary collapses to a single divider between the groups that remain. That is the difference between a separator that marks a real boundary and one that lands wherever the last drag left it.
Overflow
Every button in the two groups has a priority tier from 1 to 5. When the window narrows, tier 5 goes into the ... overflow dropdown first and tier 1 goes last. The fixed anchors are outside the groups and never overflow, and the voice recording indicator stays put while you are recording. Widen the window and they come back; a hysteresis buffer keeps them from flickering at boundary widths.
| Tier | Buttons |
|---|---|
| 1 (overflows last) | Voice recording |
| 2 | Launcher, every built-in agent button |
| 3 | Terminal, browse files, browser, dev preview, notifications, Canopy, Decisions inbox, problems |
| 4 | Repository activity, Links, plugin tray, command palette, settings |
| 5 (overflows first) | Resume session, copy context |
The launcher sits at tier 2, ahead of the individual panel buttons at tier 3, deliberately: on a fresh profile it is the only toolbar route to the agents, so evicting it before them would strand everything whose own button is not there to fall back on. A button showing a live signal is raised to tier 1 while it lasts: Problems with errors or with file watching unreliable, Canopy with an urgent ask, the Decisions inbox with a question waiting, and an agent button whose agent is waiting. Quiet tools then overflow before it.
Four buttons rewrite themselves inside the overflow menu rather than becoming a row that opens nothing. The launcher lists the agents and panel kinds that don't already have their own row there. Repository activity splits into Issues, Pull Requests and Commits entries under the forge provider's name, each with its count, or just Commits under "Git" when no provider is resolved. The plugin tray inlines its grouped contributions directly, since an unpinned plugin button has no other toolbar route. Links lists its links as menu rows, with a single Checks… row and a single Dev servers… row that open the full links launcher, the only place its deployments are listed.
The project switcher pill never overflows, but it does adapt: a scratch workspace or a folder opened without git shows no branch chip at all, while a project whose branch has not resolved yet (a detached HEAD, or a view that painted before the project bound) keeps the chip's width as an invisible placeholder rather than letting the pill jump.
Pinning, unpinning, and plugin buttons
Right-click any toolbar button, built-in or plugin-contributed, for Customize toolbar… and Unpin from toolbar. On macOS and Linux, right-clicking empty toolbar space lists every button that holds a toolbar slot as a checkbox, so a button you hid comes back from the surface you hid it on; on Windows that space is the window's drag region and shows the system window menu instead. The same pin state is what Alt+P in the launcher writes, and what Settings edits: several surfaces onto one preference.
Plugin buttons collect under the plugin tray, grouped by their owning plugin and sorted by the manifest's declared priority. Pin one out of the tray and it becomes its own toolbar button. See Plugin System.
Customizing the toolbar
Open Settings > Toolbar for the full editor, or choose Customize toolbar… from any toolbar right-click or the launcher's footer.
- Toolbar buttons lists the Left side and the Right side separately, each button once, in the grouped order the toolbar draws (launcher, agents, panels, then the rest).
- Reorder by dragging a row, or without dragging from its ... menu: Move up, Move down, and Move to right side or Move to left side. A move stays within the button's own group, exactly as a drop would.
- Show or hide with the switch on each row.
- Not on the toolbar lists everything that could have a button but doesn't, under Agents, Panels, Plugin buttons and Other buttons. Switch one on to give it a button. Agents and panels stay in the launcher either way, and plugin buttons in the plugin tray.
- The two fixed anchors do not appear in the lists.
- Reset toolbar, at the bottom, restores the default buttons, order and launcher palette options at once, with an Undo rather than a confirmation.
Preferences persist across restarts. New buttons added in a future release are merged into your layout at their default position, leaving your order intact.
Launcher palette settings
The Launcher palette section on the same tab has two settings:
- Always show dev server in launcher keeps the dev server row present even when no dev command is configured in project settings.
- Default selection picks which row is highlighted when the palette opens: None (first available), Terminal, any launchable agent, Browser, or Dev Preview. The agent list is generated from the roster rather than hard-coded, so an agent you install shows up here.
Project switcher pill
The pill in the center shows the current project name and branch. Click it for the project switcher; right-click it for project-level actions:
- Edit name and icon…: renames the project in Daintree and changes its emoji, without touching the folder on disk.
- Pin project / Unpin project: pins the project to the top of the switcher.
- Copy path: the absolute project path.
- Project settings…: opens the project-scoped settings tab.
- Stop all agents: ends every running agent across every worktree in the project. Shown only when at least one is running.
- Close project: closes it in the current window.
Picking the project you are already in from the switcher closes the palette and does nothing else. Nothing reloads, because nothing needs to.
Once you have added a remote host, a host chip sits just right of the pill. In a window on this machine it reads This Mac (This machine on Linux); in a window on a host it becomes a bordered pill, like the project pill, with a server icon and SSH · studio-01 (Boat · build-host for a cloud machine, WSL · Ubuntu on Windows). Click it for the host menu, or press Option-Command-U Control-Alt-U Control-Alt-U for a searchable host switcher. See The Host Chip.
Dock
The dock is the bar along the bottom of the window, there whether or not anything is docked. It holds panels you have moved out of the grid. Docking does not close anything: the session keeps running, and you can preview or restore it whenever. It shows the docked panels for the active worktree, plus any that belong to no worktree. Its leading + is the same launcher the toolbar carries, and right-clicking empty dock space offers the launcher inventory as a menu too.
Not every kind can be docked. Terminal, Browser, Dev preview, File viewer and File browser can; Review and Diff viewer opt out. Minimizing a panel animates from the pane into the dock chip it becomes, and back. See Three Presentations.
Dock pills
Each docked panel is a compact pill carrying its icon in the agent's brand color, a truncated title, and optionally the current command or activity in a monospace span. A state icon (a spinner while an agent is working) sits alongside. Idle and completed panels render at reduced opacity so the live ones stand out.
| Action | Behavior |
|---|---|
| Single-click | Opens a floating popover preview above the pill |
| Double-click | Moves the panel back to the grid |
| Drag | Reorders pills within the dock |
Popover preview
The popover is a live, resizable view of the panel: you get full access to it while it stays docked. Put it back in the grid with the Move to grid button in the popover's panel header, or by double-clicking that header. Escape or a click outside closes the popover without restoring.
Moving panels to and from the dock
Drag a panel header into the dock bar, use the dock button in the panel header, or use the keyboard. Option-Shift-Command-D Control-Alt-Shift-D Control-Alt-Shift-D sends the focused panel to the dock and Option-Shift-Command-G Control-Alt-Shift-G Control-Alt-Shift-G brings it back; Option-Command-M Control-Alt-M Control-Alt-M toggles it and moves keyboard focus onto the resulting pill, from which Enter or Space opens the popover. The full list, including the chords that act on every panel at once, is on Keyboard Shortcuts.
While a drag hovers the dock, the bar lights up with a drop-armed ring and the cursor switches to a copy cursor, or a no-drop cursor over anything that cannot take the panel. When the dock is empty and you start dragging, a ghost Trash pill appears at the right end so you can discard a panel in one motion. It disappears the moment the drag ends.
Keyboard navigation
Control-Tab Control-Tab Control-Tab and Control-Shift-Tab Control-Shift-Tab Control-Shift-Tab cycle every panel in the active worktree, grid panels first and dock panels after. When the cycle reaches a docked panel its popover opens automatically, so you can see the content without leaving the keyboard.
The dock bar itself is a single tab stop. Once focused, ArrowLeft / ArrowRight move between pills, Home / End jump to the ends, and Enter or Space activates the focused pill. If the dock overflows horizontally the focused chip scrolls into view. While a pill is being dragged the drag handler owns the arrow keys, so they move the pill rather than the focus.
Action containers
Set apart on the right of the dock bar, in a tray of their own, are four containers. Each is a grouped destination rather than another pill, and each counts across every worktree in the project, not just the active one; its popover splits its rows into This worktree and Other worktrees:
- Background: panels you deliberately backgrounded. Click for the list and restore individually.
- Waiting: panels whose agent is blocked on you, collected so you can clear them in one pass.
- Errors: panels whose agent session errored, so failures triage in one place instead of hiding among the rest.
- Trash: soft-closed panels awaiting permanent removal, each with a Restore action, listed most-recently-trashed first.
In compact density these show an icon and a count badge; in normal and comfortable they show a full label like "Background (3)".
Dock density
Density controls the height and spacing of dock pills. Set it in Settings > Appearance > App under Dock density, or right-click empty dock space and pick Dock density: the submenu carries a radio mark on the current value and writes the same setting.
| Option | Description |
|---|---|
| Compact | Smaller items, tighter spacing, icon-only action containers |
| Normal (default) | The standard dock |
| Comfortable | Larger items, more spacing |
The change applies immediately; no restart.
Window behavior
Cold-start animation
On launch, Daintree swaps its loading skeleton for the live workspace in one coordinated fade rather than piecemeal pop-in. The toolbar, sidebar, grid and dock settle together. On reduced-motion systems the animation is skipped and the workspace simply appears.
macOS
Daintree uses a hidden inset title bar on macOS: the traffic lights are inset and content runs to the top edge. It also uses simple fullscreen, which extends into the notch area on newer MacBooks.
Window close protection
Daintree intercepts Command-W Control-W Control-W . Rather than closing the window and killing every terminal in it, it closes the focused panel. Where that lands depends on focus: the assistant closes itself, an open dialog or palette dismisses its topmost layer, and a focused grid or dock panel closes that panel.
Window state
Size, position, and whether the window was maximized or fullscreen are remembered per project path, so each project reopens with its own geometry. With no saved state for a project, the new window cascades 30px from the most recently used one.
Window titles
Each window's native title names the project it is currently showing, prefixed with a count of agents waiting on you, so (2) payments-api in Mission Control, the Dock menu, or the Windows taskbar tells you both which window it is and whether it wants attention. A window sitting on the project picker falls back to Daintree. A window on a remote host adds the host's name after the project's.
The name is resolved from that window's own view, never from a process-global "current project" pointer, which is what makes two open windows stay distinct. The app name is deliberately not appended after the project name: the Dock already groups every window under one icon, so repeating it would cost the space that tells the windows apart.
Multiple windows
You can open several Daintree windows at once, each on a different project, and work across them side by side. A project is live in one window at a time: opening a project that another window already has brings that window forward instead of opening it twice.
- A new, empty window: Option-Shift-Command-N Control-Alt-Shift-N Control-Alt-Shift-N or File > New Window. It opens on the Welcome Screen.
- A project in a new window: File > Open Project in New Window…, a Cmd-click (Ctrl-click on Windows and Linux) in File > Open Recent, the Welcome Screen's Open in new window…, Open in: New window in the clone and create-folder dialogs, or the project switcher: right-click a project and choose Open in new window, or highlight it and press Command-Enter Control-Enter Control-Enter . The footer shows the hint while you hold the modifier. A project another window holds offers Go to window instead.
- From outside Daintree: a folder opened from the Dock, your file manager or
daintree /path/to/repowhile Daintree is running fills an empty window or opens a new one. By default it never replaces the project in a window you are using; Settings > General > Overview > Opening folders changes that.
The full rules, including the Open folders in a new window setting, are on Projects.
Windows can also sit on different machines. A window on a remote host shows that host's files, Git, terminals and agents, not this machine's, and the two sit side by side like any other windows. See Open a Host in a New Window.
Relaunch restores your windows
Daintree records which project each window was showing when the app last ran, and a relaunch rebuilds the whole set, not just one window. With Restore live projects on (the default), the projects that were running in the background come back too; see Restoring live projects. Windows come back most-recently-focused first, and a window that was sitting on the project picker restores as a picker window rather than being dropped. A window that was on a remote host is reopened on that host and project when it can be reached, and otherwise opens on this machine with a Retry; see After Daintree Restarts.
The restore is capped at eight windows. The cap is applied after the focus ordering, so what gets dropped is whatever you had focused longest ago, and a corrupt or hand-edited manifest cannot launch an unbounded fleet of renderers at startup.
Source reference: pinned launcher entries, launcher inventory, launcher bands, which window an open lands in, and project view lifecycle.