Customize Shortcuts
Changing Daintree keyboard shortcuts: opening the editor, assigning and removing bindings, recording chords, what happens on a conflict, per-platform differences, unbound actions, and resetting to defaults.
Customizing shortcuts
Open Settings with Command-, Control-, Control-, and switch to the Keyboard tab, or press Edit shortcuts at the foot of the shortcut reference dialog (Command-K, then Command-S, or Command-/ Control-K, then Control-S, or Control-/ Control-K, then Control-S, or Control-/ ). At the top sit a search field (Search by action, key or category) and an All / Modified filter; below them the bindings are grouped by the same categories, in the same order, as the reference dialog. Each row shows the action, its keys, and a short scope note when the binding only works in one place (In dev preview, In an expanded worktree card, In a diff viewer). Under the bindings come three sections: Fixed shortcuts (the worktree-list and drag-handle keys, listed so you know they exist but not rebindable), Gestures (the double-tap Shift switch for Canopy), and Backup and reset.
- Record a combo: click a row to open its editor, which starts recording straight away, and press the keys. After the first keystroke the recorder waits one second for a second one (Press second key or wait to finish): press one and you get a chord, wait and you get the single combo. Recording owns every key, so pressing the combo an action already uses records it instead of firing it. Switching away from the window mid-capture cancels rather than saving a combo with unknowable modifier state. Save applies the recording; Cancel leaves the binding as it was.
- Remove shortcut: in the editor, removes the action's keys without recording new ones, leaving the action reachable only from the palette and menus. The reference dialog then shows it as Not set.
- Reset to default: a customized row carries the modified marker at its left edge and a reset button that puts just that row back to the shipped binding. The Modified filter lists only those rows.
- Reset all shortcuts: under Backup and reset. Reset all asks first, suggesting you export a profile to keep a copy, then puts every customized shortcut back to its default.
Conflicts
The recorder checks a candidate combo against every registered binding in an overlapping scope and reports two distinct outcomes:
- Conflict: the same combo already belongs to another action. The editor lists it under Conflicts with, with an inline Unbind button; clicking it frees the combo and raises a five-second toast carrying an Undo. In Settings > Keyboard a conflict warns rather than blocks, so you can still save.
- Shadowed: a chord-prefix overlap, such as binding Command-K Control-K Control-K on its own while chords start with it. Unbinding cannot resolve this, because neither combo equals the other, so Daintree names the relationship in the direction it applies (shadows this chord, or is shadowed by this chord) and leaves the decision to you.
Scope matters here: a global candidate is checked against both global and scoped bindings, while a scoped one only clashes within its own scope and the global set. That is why a scoped binding can reuse a combo that a global binding already holds without disturbing it everywhere else.
Scopes and priority
Every binding carries a scope and a priority; candidates outside the active scope are excluded, then the highest-priority match wins. This lets a focused surface such as Dev Preview keep its own keys while global shortcuts remain available outside it.
| Scope | Active when |
|---|---|
global | Always. |
dev-preview | A dev preview panel has focus. |
diff | Focus is inside a diff viewer. |
worktreeGrid | A worktree card's session list is expanded (Settings > Keyboard calls these rows In an expanded worktree card). A bare key never fires from inside a terminal, which is what makes the bare X X X arm toggle safe. |
| Priority | Source |
|---|---|
| 0 | Shipped default |
| 1 | Plugin contribution |
| 5 | Elevated default: a binding that must beat an ordinary one, such as the fleet broadcasts and region focus |
| 10 | Elevated global defaults, such as close-terminal and workspace switching |
| 20 | Scoped surface default, such as Dev Preview reload |
Plugins can contribute keybindings at priority 1, and registration rejects collisions with existing effective bindings, including your rebinds. An override changes the action's effective combo; it does not automatically assign priority 10. A binding may also carry a when clause evaluated against live context: whether a terminal is focused, a modal or palette is open, the fleet is armed or has a waiting agent, the sidebar is visible, or Canopy is hidden. The shipped Open Canopy binding uses the last one, which is why hiding Canopy turns its key back into an ordinary keystroke.
Shortcut profiles
Under Backup and reset > Shortcut profile, Export writes a JSON file containing only your overrides, not the full default table, so profiles stay small and survive version changes. Import merges a file's overrides onto your current ones: an action the file names takes its keys from the file, and every other customization stays as it is.
{
"schemaVersion": 1,
"exportedAt": "2026-08-18T12:00:00.000Z",
"app": "daintree",
"overrides": {
"terminal.new": ["Cmd+Alt+T"],
"git.stageAll": ["Cmd+K Cmd+G"]
}
} On import Daintree checks the file size (100 KB maximum), rejects a mismatched schemaVersion outright, and validates the shape before applying anything. An empty list for an action means it is deliberately cleared. An override for an action this version does not have does not fail the import; it simply has nothing to bind to, so a profile stays usable across releases. A binding whose default moved to a successor action carries your override with it, so a rename does not silently strand a rebind.
Keyboard shortcut overrides also travel in the wider configuration bundle from Settings > Import & export, alongside agents, themes and other portable settings.