Skip to main content

Sounds and Settings

Agent notification events and the sounds attached to them, dampening, the full notification settings reference, and the per-project overrides that let one repository be louder or quieter than the rest.

Updated
Reviewed

Agent Notification Events

Completion

Agent completed sends an OS notification when a watched agent finishes. Off by default: completion is less urgent than an agent needing you. The OS notification goes out about 2 seconds after the agent finishes, and agents finishing together coalesce into one notification ("N agents finished their tasks") and one sound.

Waiting

Agent waiting for input is on by default and covers watched agents. It fires immediately with no debounce; a 200ms burst window catches simultaneous events. Two grace periods prevent false alarms: a 5-second spawn grace suppresses alerts from agents that start directly in a waiting state, and an 8-second boot grace stops agents that were already waiting from replaying their alerts when the app launches. The alert is held back while you are present and looking at that agent's worktree, and it is withdrawn once the agent stops waiting.

Waiting escalation

Escalate if still waiting sends a second notification when a docked agent has been waiting longer than the Escalation delay, for background agents you are not actively watching. It needs Agent waiting for input on, but not a watch. Off by default; the delay is 1, 3 (default), 5 or 10 minutes. Several docked agents still waiting when it fires are grouped into one notification ("N agents have been waiting for input").

Note

Escalation applies only to docked agents, not to agents visible in the panel grid, and it fires even when the window is focused: the point is to catch background work you have lost track of.

Working pulse

A periodic audio cue while an agent is actively working, giving you an ambient sense of progress without watching the UI. It covers watched agents, and docked agents while Escalate if still waiting is on. Off by default, and it needs Play sound. It waits 10 seconds, then plays at random 8–10 second intervals on a separate channel that bypasses dampening, and stops when the agent leaves its working state or you focus the terminal.

Each pulse is detuned by a random amount up to ±15 cents, so consecutive pulses vary slightly. It is also gated on your OS Focus state: a system-level DND silences the pulse.

All-clear

Plays when every concurrently active agent has stopped working; an agent waiting for input counts as stopped. It requires at least two agents to have been working at the same time. The sound obeys Enable notifications, Play sound, Do Not Disturb, Quiet Hours, and OS Focus. Play sound is off by default. A single-agent completion follows the completion settings instead. A 500ms debounce confirms the last one really is the last one. It always plays at full volume regardless of dampening. Flash when agents stop working adds a brief window flash at the same moment, with or without sound.

Sound System

Daintree ships 14 sounds. Playback routes through the Web Audio API when a window is available and falls back to OS-level playback when no renderer is active.

SoundUsed for
chimeGeneral notification chime
completeAgent completed its task
waitingAgent waiting for input
errorError events
pingWaiting escalation (default)
pulseWorking pulse
all-clearAll agents finished
git-commitGit commit executed
git-pushGit push succeeded
git-push-errorGit push failed
worktree-createWorktree created
worktree-deleteWorktree deleted
agent-spawnedNew agent process started
context-injectedContext injection completed

Most sounds ship with three variants, picked randomly with no immediate repeats, so a sound you hear often does not become a tic. Only error, git-push-error, pulse and worktree-delete are single-variant.

The four sound choices in settings (Completed sound, Waiting sound, Escalation sound and Working pulse sound) each pick from six: Chime, Ping, Complete, Waiting, Error and Pulse. The git, worktree, agent-spawn, context and all-clear sounds are fixed.

Dampening

When events fire in quick succession the system applies exponential volume decay: each consecutive sound plays at 70% of the previous volume, down to a 10% floor, resetting after 2 seconds of silence. At most 3 voices play at once, and when the pool is full, lower-priority sounds are dropped. Priority runs error, waiting, chime and complete, ping, pulse.

Chord detection handles the specific case of several agents completing within 2 seconds: rather than overlapping completion sounds at decaying volumes, one unified chord plays at full volume.

The Preview button beside each sound selector in settings always plays at full volume, bypassing dampening entirely: you are auditioning the sound, not simulating a burst.

UI feedback sounds

A separate category with its own switch, UI feedback sounds, off by default: short cues for git commit and push, worktree create and delete, agent spawn, and context injection. These also require the master Play sound switch. Turning that switch off silences UI feedback as well as agent sounds.

Settings Reference

Global notification and sound settings live in Settings > Notifications, in three sections. Agent notifications holds Enable notifications, the completion, waiting and escalation settings, and Flash when agents stop working. Sound holds Play sound, the four sound choices, Working pulse and UI feedback sounds. Quiet hours holds the schedule. Inbox grouping is the Group by project or worktree option in the inbox's own menu, and the two idle-terminal rows sit under Settings > General > Hibernation > Background projects.

Every row carries a reset button while it differs from the default. While Enable notifications is off, everything else on the page is greyed out.

SettingKeyDefaultScopeDescription
Enable notificationsenabledOnGlobal onlyMaster toggle. Hides the bell and suppresses toasts and OS alerts. History still records.
Agent completedcompletedEnabledOffPer-projectOS notification when a watched agent finishes
Agent waiting for inputwaitingEnabledOnPer-projectOS notification when a watched agent needs input
Escalate if still waitingwaitingEscalationEnabledOffPer-projectSecond notification when a docked agent is still waiting
Escalation delaywaitingEscalationDelayMs3 minPer-project1, 3, 5 or 10 minutes
Flash when agents stop workingflashEnabledOffGlobal onlyFlash on a multi-agent all-clear; follows notification suppression and reduced-motion preferences
Play soundsoundEnabledOffPer-projectMaster sound toggle, including UI feedback and all-clear
Completed soundcompletedSoundFileCompletePer-projectSound for completion
Waiting soundwaitingSoundFileWaitingPer-projectSound for waiting
Escalation soundescalationSoundFilePingPer-projectSound for escalation
Working pulseworkingPulseEnabledOffPer-projectPeriodic cue while a watched agent, or a docked one with escalation on, works
Working pulse soundworkingPulseSoundFilePulsePer-projectSound for the working pulse
UI feedback soundsuiFeedbackSoundEnabledOffGlobal onlyUI feedback cues for git, worktree and agent lifecycle
Mute on a schedulequietHoursEnabledOffGlobal onlyEnable the scheduled quiet window
Hours (start)quietHoursStartMin1320 (22:00)Global onlyWindow start, minutes past midnight
Hours (end)quietHoursEndMin480 (08:00)Global onlyWindow end, minutes past midnight
Active daysquietHoursWeekdays[] (every day)Global onlyDays the schedule applies; empty means every day
Group by project or worktree (inbox menu)groupByContextOffGlobal onlyGroup the inbox under its projects and worktrees
Notify me about idle terminalsidleTerminalNotify.enabledOnGlobal onlyRecord when every terminal in a background project is idle
Remind afteridleTerminalNotify.thresholdMinutes60Global onlyIdle threshold. Presets 30m, 1h, 2h, 4h; range 15–1440 minutes.

Retention is not a setting: read entries are kept for 7 days, archived entries for 30 days, and unread entries indefinitely.

In a window on a remote host, the page marks which settings belong to the host (when agents notify, quiet hours, the working pulse) and which to the machine you are sitting at (sound, the flash). See Notifications on the remote hosts page.

Per-Project Overrides

Open Settings, switch the sidebar's scope control to Project, and choose the Notifications tab. Each row shows the value that applies to this project and where it comes from: Using global default · On while it inherits, or Set for this project · global default is Off once you change it. Changing a row is what creates the override; the row's reset button removes it, so the row inherits again. Resetting a row never clears another row's override: an escalation delay you chose for this project survives resetting the waiting switch. Mute project notifications from a toast or inbox menu is the one-click shortcut for turning the completed and waiting rows here off together.

Reset the changed row to inherit its global value again.

Overridable per project: Agent completed, Agent waiting for input, Escalate if still waiting and its delay, Play sound, the completed, waiting and escalation sounds, and Working pulse with its sound.

Global-only, and not overridable: Enable notifications, Flash when agents stop working, UI feedback sounds, quiet hours, inbox grouping, and both idle-terminal settings.

Warning
The global master toggle is a kill-switch. With enabled off, all toast and OS delivery is suppressed for every project regardless of per-project overrides, though the inbox keeps recording, and the project's Notifications tab says nothing there takes effect. If one project is not notifying you, check the global toggle first.
Note
Per-project notification overrides are stored locally on your machine and are not committed to the repository, so everyone configures their own without affecting anyone else. For the full picture of what Daintree stores per-project versus per-machine, see Projects.