Daemon Service Cold-Start Prompt [Gradual Rollout]

What

Interactive prompt to install the daemon as a persistent system service.

Status

Feature-flagged behind tengu_quiet_harbor (default false — defaults to "transient" mode where daemon spawns on demand without asking).

Details

When the flag is enabled (set to return "ask"), the interactive installation prompt appears
Can be forced via CLAUDE_CODE_DAEMON_COLD_START=ask environment variable or settings.daemonColdStart

Read from

Feature flag

tengu_quiet_harbor Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.120: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.120. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since

Flag reading moved 10 Sep 2026 The flag server now returns off for tengu_quiet_harbor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

Flag reading moved 10 Sep 2026 The flag server now returns nothing at all, having stopped carrying it for tengu_quiet_harbor, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.120 →

The build it came inv2.1.120

24 Apr 2026 · 27 entries, this one is #27.

Either side of it

v2.1.119Older
v2.1.121Newer

Open the release →

Names in this entry

flagtengu_quiet_harbor
Default false. Supplies the background daemon cold-start mode when neither CLAUDE_CODE_DAEMON_COLD_START (transient or ask) nor the daemonColdStart setting is set: true gives ask, false gives transient. With ask, when no background daemon is running and the install prompt has not been dismissed, Claude Code (under further conditions) returns an install request telling you to run claude daemon install instead of spawning a transient daemon.
envCLAUDE_CODE_DAEMON_COLD_START
What to do when the background daemon is needed and none is running. A value of transient or ask overrides the daemonColdStart setting; any other value is ignored, and with neither set the default is ask when the tengu_quiet_harbor flag is on and transient otherwise. With ask, Claude Code returns a prompt to run claude daemon install instead of spawning a transient daemon, as long as an extra check passes and the install prompt has not been dismissed.
settingdaemonColdStart
What happens when the background daemon is needed and none is running. With ask, if installing the daemon as a persistent service is possible here (among other checks, CLAUDE_CONFIG_DIR must be unset) and the install prompt has not been dismissed before, Claude Code returns an offer to install it (No background daemon is running. Run 'claude daemon install'...) instead of spawning one; otherwise, and with transient, it spawns a daemon for this login session. The env var CLAUDE_CODE_DAEMON_COLD_START (transient or ask) overrides the setting, and with neither set the default is ask when the tengu_quiet_harbor flag is on and transient otherwise.

Is this right?