Keyboard Shortcuts

Daintree ships 116 keyboard actions from a single table that both the app window and the native menu bar read. The renderer seeds its keybinding service from it and the main process derives its menu accelerators from it, so a menu item can never claim a chord the keyboard does not actually fire.

Two surfaces expose those bindings at runtime. The shortcut reference dialog (Command-K, then Command-S, or Command-/ ⌘K ⌘S or ⌘/ Control-K, then Control-S, or Control-/ Ctrl+ K Ctrl+ S or Ctrl+ / Control-K, then Control-S, or Control-/ Ctrl+ K Ctrl+ S or Ctrl+ / ) is read-only and shows your effective bindings, including rebinds and anything a plugin contributed. Settings > Keyboard (Command-, ⌘, Control-, Ctrl+ , Control-, Ctrl+ , ) is where you record, unbind, reset, and import or export profiles. This page lists the shipped defaults; the dialog is always the current answer for your install.

Notation and platform mapping

Every shortcut on this site is written for one platform at a time. Pick yours and the whole page follows — including the tables below, and every shortcut on every other page. The choice is remembered, so you only make it once.

• Each platform is written the way it writes itself: macOS uses modifier glyphs in Apple's order with no separators, while Windows and Linux spell the keys out and join them with +. The Pilot binding is Option-Command-O ⌥⌘O Control-Alt-O Ctrl+ Alt+ O Control-Alt-O Ctrl+ Alt+ O either way.
• A row showing Control on macOS (Control-Shift-J ⌃⇧J Control-Shift-J Ctrl+ Shift+ J Control-Shift-J Ctrl+ Shift+ J ) means the physical Control key, which is a different key from Command. On Windows and Linux it collapses onto the same chord as a Command row — which is why the diagnostics family uses Control rather than a letter already spent.
• A chord is two keystrokes in sequence, shown with a gap between them: Command-K, then Command-G ⌘K ⌘G Control-K, then Control-G Ctrl+ K Ctrl+ G Control-K, then Control-G Ctrl+ K Ctrl+ G means press the first, release, then press the second. Every shipped chord starts with the same first keystroke.
• A pending chord does not time out. It waits until you complete it, cancel it with Escape Esc Escape Esc Escape Esc , blur the window, or change scope. Press Command-K ⌘K Control-K Ctrl+ K Control-K Ctrl+ K on its own and the command HUD lists every completion.

Navigation

Repeat last action re-runs the last action you triggered through a palette or shortcut against the same target, without reopening the palette. Focus mode hides the worktree sidebar and the Daintree Assistant together so the panel grid takes the whole window; the same chord brings them back.

F6 F6 F6 F6 F6 F6 is the one bare key that still reaches the app while a terminal has focus: it is the deliberate escape hatch out of a focused terminal for keyboard-only navigation. See terminal key ownership.

Terminals and panels

Moving focus in the grid

Moving panels and docking

Other panels

The diagnostics family uses a literal Ctrl on all three platforms and toggles on J, not D. Shift-Command-D ⇧⌘D Control-Shift-D Ctrl+ Shift+ D Control-Shift-D Ctrl+ Shift+ D now opens changes for the focused worktree, and off macOS the command modifier is Control — so a diagnostics binding on D would land on that same physical chord, and one of the two would silently shadow the other. See Diagnostics.

Agents

Only three of the shipped agents carry a default launch shortcut. Every other built-in agent has a registered action with no combo, so it shows in the reference dialog as unbound and is free for you to claim. See AI Agents for the roster and Agent States for what waiting, working, and exited mean — the jump shortcuts above navigate by exactly those states.

The all-projects jump (Option-Shift-Command-/ ⌥⇧⌘/ Control-Alt-Shift-/ Ctrl+ Alt+ Shift+ / Control-Alt-Shift-/ Ctrl+ Alt+ Shift+ / ) walks projects in sidebar order, switches to the first one holding a waiting agent, and focuses it. It wraps from the bottom back to the top, so repeated presses step through every project without leaving the keyboard.

Fleet

Fleet arming selects a set of agent terminals and broadcasts one action to all of them. See Fleet for the full model.

The bare X X X X X X arm toggle is scoped to the worktree grid, so it only fires when focus is outside a terminal — inside one it is just the letter X. Both Option-Command-A ⌥⌘A Control-Alt-A Ctrl+ Alt+ A Control-Alt-A Ctrl+ Alt+ A and the terminal-category Shift-Command-B ⇧⌘B Control-Shift-B Ctrl+ Shift+ B Control-Shift-B Ctrl+ Shift+ B arm every eligible terminal in the current worktree; they are two bindings onto the same effect, kept because the fleet ribbon and the terminal surface each teach their own.

Interrupt is not a rebindable entry in the keybinding table. It is a double-tap handler, because a single binding would collide with the escape stack that dismisses modals. The first bare Esc passes through untouched so xterm still broadcasts a raw escape to every armed agent; the second, within 350 ms, is consumed and translated into the fleet interrupt. Auto-repeat from a held Esc is ignored, and a double-tap inside an ordinary text input belongs to that input. A single Esc still clears a pending fleet confirmation or disarms the fleet.

There is a second way to reach it. Command-Escape ⌘Esc Control-Escape Ctrl+ Esc Control-Escape Ctrl+ Esc is the Fleet exit chord, and it is held for 350 ms before it fires; a second Command-Escape ⌘Esc Control-Escape Ctrl+ Esc Control-Escape Ctrl+ Esc inside that window cancels the exit and interrupts instead. The second press has to carry the modifier — a bare Esc takes the bare-Escape path above and lets the pending exit through. Neither Escape chord is a rebindable entry: both are handled by a dedicated window listener so they can sidestep the escape stack. See Fleet.

Worktrees

See Worktrees, Worktrees Overview, and CopyTree.

Worktree sessions

These act on every session in the active worktree at once.

Projects and Pilot

Pilot sits one step further out than the project switcher beside it: the switcher picks a project, Pilot shows every agent run across every project at once. Switch to last project walks your most-recently-used stack rather than sidebar order — the equivalent of Alt-Tab for projects. There is no forward-cycling counterpart; the earlier Option-Shift-Command-= ⌥⇧⌘= Control-Alt-Shift-= Ctrl+ Alt+ Shift+ = Control-Alt-Shift-= Ctrl+ Alt+ Shift+ = binding was removed.

Git

Portal

Scoped bindings: they resolve only while the portal browser has focus, and they outrank the global bindings that share their combos. See Portal Browser.

Dev preview

Also scoped: Command-R ⌘R Control-R Ctrl+ R Control-R Ctrl+ R reloads only the dev preview panel that has focus, and does nothing anywhere else.

View

Voice

The two toggles differ by target, not by mode. Shift-Command-V ⇧⌘V Control-Shift-V Ctrl+ Shift+ V Control-Shift-V Ctrl+ Shift+ V dictates into whichever panel input has focus; Option-Shift-Command-V ⌥⇧⌘V Control-Alt-Shift-V Ctrl+ Alt+ Shift+ V Control-Alt-Shift-V Ctrl+ Alt+ Shift+ V dictates into the Daintree Assistant without needing to focus it first. Pause suspends a session without ending it, so the transcript continues where it left off. See Voice Input.

Help, app, and system

Windows-only additions

Two extra defaults ship on Windows, matching what desktop users there already expect: Ctrl+F4 also closes the focused terminal, and also closes the active portal tab. They are additions, not replacements — the cross-platform bindings still work, and both rows above already show the alternative when Windows is selected.

These two are written out rather than rendered, because they exist on one platform only. A rendered shortcut follows whichever platform you have selected, which would spell this one ⌃F4 on macOS — a chord that does not exist.

Surface-local gestures

Not every key in Daintree is a keybinding. A surface-local gesture is a key handled by one panel, tree, or palette while that surface has focus. It is deliberately not a registered action, because the command only means anything in the presence of local state the global registry cannot see — which row is selected, which file is current, which tree owns the cursor. The consequence for you: these do not appear in the shortcut reference dialog, they are not rebindable, and they cannot conflict with a global binding.

Command-I ⌘I Control-I Ctrl+ I Control-I Ctrl+ I is the clearest example of why the distinction exists. The global registry dispatches in the capture phase, before any tree could tell it which row is active, so an action would have to re-infer the focused browser, its worktree, and its base path. The gesture stays with the tree. Shift-Command-I ⇧⌘I Control-Shift-I Ctrl+ Shift+ I Control-Shift-I Ctrl+ Shift+ I , one Shift away, is a real global binding that injects context into the focused terminal — the gesture requires Shift and Alt to be absent rather than merely ignoring them, so the two never both fire.

Terminal key ownership

A focused terminal is a program in its own right, and the keys that program needs cannot also be app shortcuts. One shared policy decides this, consulted by both the window's capture handler and xterm's own key handler, so the two layers can never disagree about who owns a key.

While a terminal has focus:

• Shortcuts without a modifier reach the terminal, not the app. F6 F6 F6 F6 F6 F6 region cycling is the deliberate exception, so keyboard-only users always have a way out.
• The readline family is reserved. Bare Ctrl with a b d e f h j k l n p r t u w y goes to the PTY. That includes Ctrl+J, Ctrl+L, Ctrl+T, and Ctrl+Y, which are accept-line, clear-screen, transpose, and yank — every bit as load-bearing as the rest.
• A pending chord still wins. If you have already pressed Command-K ⌘K Control-K Ctrl+ K Control-K Ctrl+ K , the completion resolves as a shortcut even inside a terminal, because you opened that chord deliberately.
• Tab and Shift+Tab pass through to the PTY for shell completion and TUI navigation. Daintree cancels the browser's native focus traversal but still lets xterm emit the tab sequence, so completion works without focus jumping out of the panel.
• Bare F11 no longer toggles fullscreen. Same mechanism: the DOM path is cancelled so the key cannot reach the window's fullscreen accelerator, and the F11 sequence still reaches the PTY. Use the View menu, or Ctrl+Cmd+F on macOS, to go fullscreen from a focused terminal.

Clipboard keys are where the platforms genuinely part ways.

The Cmd+K command HUD

Press Command-K ⌘K Control-K Ctrl+ K Control-K Ctrl+ K and release, and a searchable command HUD opens anchored to the bottom of the window. It lists every completion of that layer — the whole curated power-command set — grouped by category, each row carrying its second key as a chip.

• Type to filter. The query matches both the command's label and its key chip.
• Arrow keys move the selection, Enter runs it, and clicking a row does the same.
• Holding the modifier still completes the chord. Pressing Command-G ⌘G Control-G Ctrl+ G Control-G Ctrl+ G while the HUD is open stages your changes exactly as it would have if you had typed the chord quickly. The HUD is a discovery aid layered onto the chord, not a mode you have to leave.
• Esc cancels and hands focus back to whatever had it — unless the completed chord opened and focused something else, in which case the HUD leaves that alone rather than yanking focus back.

Type the full chord quickly and the HUD never appears, so it stays out of the way once a chord is in your fingers.

The shortcut reference dialog

Open it with Command-K, then Command-S, or Command-/ ⌘K ⌘S or ⌘/ Control-K, then Control-S, or Control-/ Ctrl+ K Ctrl+ S or Ctrl+ / Control-K, then Control-S, or Control-/ Ctrl+ K Ctrl+ S or Ctrl+ / ; both run the same action. It is read-only, and it is the surface to trust when this page and your install disagree — it renders your effective bindings, so rebinds, imported profiles, and plugin contributions all show up, and it updates live as you change them in Settings.

Rows are grouped by category, ordered Terminal, Agents, Worktrees, Panels, Navigation, Help, System, then everything else alphabetically. Each row carries the action's description, a scope label when the binding is not global, and the current combo as a chip.

The search field does two things:

• Fuzzy text search across descriptions, keywords, action ids, and categories. Type commit to find the git chord; type unbound to list every action shipping without a combo, which is how you hunt for a free slot.
• Chord-prefix matching when the query looks like a chord. Type Cmd+K and the list narrows to every binding starting with it.

Customizing shortcuts

Every binding above can be reassigned, and any action without one can be given a combination. Opening the editor, recording a chord, resolving a conflict, and resetting to defaults are covered at Customize Shortcuts.

How Daintree teaches its shortcuts

Two mechanisms exist so you learn bindings without reading this page.

• Shortcut hints. When you run an action by clicking — a toolbar button, a menu item, a panel control — Daintree shows the keyboard equivalent beside the pointer. It fires on the 1st, 2nd, 4th, 8th, 16th, and 32nd time you use that action and then stops for good, so it teaches on a curve rather than nagging. Hints are suppressed when the action opened a modal that would cover them.
• Undo for a vanishing region. Pressing Command-B ⌘B Control-B Ctrl+ B Control-B Ctrl+ B by accident hides the whole worktree sidebar with nothing on screen connecting the disappearance to what you pressed. When a bare keypress hides a region, Daintree raises a 30-second notice naming the combo that did it and offering an Undo. It appears at most three times for a given action and combo, then assumes the gesture is yours. Only keypresses get this: a menu item or toolbar button names itself at the moment of the click.

Accessibility

Shortcuts are exposed to assistive technology through the W3C aria-keyshortcuts attribute, so NVDA, JAWS, and VoiceOver announce the combo alongside the control's label — formatted Meta+Shift+P on macOS and Control+Shift+P elsewhere.

Chords are deliberately left out of aria-keyshortcuts: the specification has no way to express a sequence of keystrokes, so a chord written into that attribute would be announced as something the user cannot press. Chords stay discoverable through the command HUD and the reference dialog instead.

Tooltips across the toolbar, panel headers, and dock render shortcuts as key chips. The visible chip is marked aria-hidden and a single screen-reader span carries the readable label, so the announcement never doubles.

F6 F6 F6 F6 F6 F6 and Shift-F6 ⇧F6 Shift-F6 Shift+ F6 Shift-F6 Shift+ F6 cycle focus between the app's regions and are the one bare-key exception to terminal key ownership, so a focused terminal is never a keyboard trap.