Settings
How Daintree's 24 global settings tabs and 9 project tabs fit together: the scope switcher, the override-vs-inherit model, cross-scope search, sidebar indicators, and exporting or importing portable configuration.
Open Settings with Command-, Control-, Control-, , or click the Settings control in the toolbar. The dialog is a left sidebar of grouped tabs and a content panel on the right. When a project is open, a scope switcher in the sidebar header toggles between Global and Project settings.
Settings split into two scopes:
- Global Settings apply to Daintree as a whole, regardless of which project is open. They cover 24 tabs across the General, Terminal, Assistant, Integrations, and Support groups.
- Project Settings cover 9 tabs and layer on top of the global values for one project only. They only exist while a project is open.
In a window on a remote host, every setting belongs either to the host or to the machine you are sitting at. Each page, or each section of a page that has both, says whose values it shows: Settings on studio-01, or This Mac (This machine on Linux). Nothing is synced between machines. See Settings and Accounts.
Opening Settings from the toolbar or the menu always lands on global scope, whichever tab you were last on there. Switching scope takes you to the tab you were last using in that scope, because the two scopes hold different tabs and dumping you on a mismatched one would just cost a click. A search result, or any action that deep-links a specific tab, opens directly on it in the right scope.
Override and inherit
Project settings do not replace global ones: they sit in front of them. Most project fields have a global default behind them, and the field tells you which one is in play. An overriding field carries a modified bar and a reset control beside its label. The inherited-value description stays visible, so you can see what resetting will restore. Clearing an overridden field reverts it to inherited, so most of the time you don't need the reset button at all.
That is the model for scalar fields. Environment variables use a related but distinct shape: a read-only inherited block above the editable project rows, with pills marking which inherited keys the project has taken over. Both are documented on the Project Settings page.
Search
With the Settings dialog focused, press Command-F Control-F Control-F or / to jump to the search field. Matching is fuzzy across every setting name, description, and keyword, so partial matches and minor typos still find the right result.
As you type, match count badges appear next to each sidebar tab showing how many results that tab holds. The content panel is replaced with a scrollable list of result cards. Each card leads with a scope chip (Global or Project) so you can see which scope the result lives in, then a breadcrumb path (Tab › Subtab › Section), the setting title with matches highlighted, and a description. A setting that depends on a disabled feature carries a Requires <feature> pill, so you know the click will land on a page gated behind an enable toggle.
Arrow keys move through results, and Enter opens the right scope and tab, scrolls to the matching row and focuses its control. Esc clears the query; a second Esc blurs the search field.
The @modified filter
Type @modified (or the short alias @mod) in the search box to show only settings that differ from their defaults. It combines with keywords: scrollback @modified narrows to modified scrollback-related settings.
The filter tracks selected settings in General, Panel grid and Appearance. It does not cover every setting or project overrides. With no tracked changes, the empty state names that limited coverage.
@modified query follows the current scope. Text searches can still return results across scopes, but only tracked global settings currently contribute modified results.Sidebar indicators
Three kinds of marks can appear on a tab's icon in the sidebar. They're independent of which tab you have open, and they update live as you change settings.
- Modified marker: at least one setting on that tab differs from its default. This is the modified indicator.
- Error marker: an amber triangle means the tab has reported a validation error. Its shape differs from the modified dot, so the two remain distinguishable without color.
- Match count badge: only visible while you're searching. Shows how many results the active query matches in that tab.
When a tab has both a modified setting and a validation error, the error marker wins. The error marker clears itself as soon as the underlying error resolves. Leaving the tab does not clear it. A visited panel stays mounted, so the error travels with you until you fix it or close Settings.
Three tabs currently track modified state:
| Tab | Triggers the modified dot when |
|---|---|
| General | Any Display subtab toggle differs from its default (Project Pulse off, Developer Tools on, or either Agent Highlights toggle on) |
| Panel Grid | Selected performance, input, grid layout, split ratio, or scrollback settings differ from their defaults |
| Appearance | Dock Density is set to Compact or Comfortable (the default is Normal) |
Validation-capable tabs include Appearance, Worktree, Environment, Code Forge, Voice Input, Links, MCP Server, Daintree Assistant, and the project Worktree Setup tab. They raise it when their stored values or provider list fail to load, or when a field on them is invalid: an unparseable env key, a broken worktree path pattern. More tabs can opt in over time, so treat the error marker as the general signal that something on that tab needs attention, not as a fixed list.
Move configuration to another machine
Open Settings > Import & export. Choose Export… to save a versioned JSON bundle, then Import… on the destination machine. Both actions are also searchable in the command palette. This transfers selected global configuration:
- Custom agent definitions and per-agent settings, including presets
- Keyboard shortcut overrides
- App theme preferences and custom app themes
- Notification preferences
- The global worktree path pattern
- Global recipes
The bundle does not transfer projects, open panels, terminal history, installed plugins, repository-owned configuration, or credential stores. Global environment variables are not a bundle section. The app-wide Skip permission prompts and Use alternate screen overrides also stay on the destination machine; per-agent settings are portable.
Before import, a preview names the file and counts additions and replacements in each affected section. Confirming merges those entries into existing configuration: matching IDs or setting keys can be replaced, while entries absent from the bundle stay as they are. The dialog confirms the bundle as a whole; it does not offer section checkboxes. When values will be replaced, the preview offers Export a backup… to save the destination's current configuration before importing. Daintree keeps no persistent pre-import backup.
The result reports applied, already-matching and skipped entries. Unsupported actions, invalid agent definitions or sound files unavailable on the destination can be skipped while other entries apply. An import failure triggers an attempt to restore the in-memory pre-import snapshots and keeps the dialog available to retry; inspect the error if restoration also fails. Unknown sections are ignored, but a newer bundle format is rejected with a request to update Daintree.
Export and import copy configuration to another machine. To run your work on another machine instead, from the window you already have, see Remote Hosts. A host keeps its own settings; nothing is synced between machines.
For the exact portable fields and validation rules, see the configuration bundle service, bundle parser and secret omission, and import preview.