When no background daemon is running and one is needed, Claude Code now interactively asks whether to install it as a persistent system service.
No background daemon is running.
Installing it as a service keeps scheduled and remote-control workers running across reboot.
Install as a service now? [Y/n/never, or 'once' for this login session]Y(default): installs a launchd (macOS) or systemd (Linux) service that persists across rebootonce: spawns a transient daemon for the current login session onlynever: remembers the dismissal and won't ask again (spawns transient)n: does nothing — the command fails with the original "no daemon running" error- Controlled by the
tengu_quiet_harborfeature flag (determines whether mode is "ask" or "transient") - Also configurable via
CLAUDE_CODE_DAEMON_COLD_STARTenvironment variable orsettings.daemonColdStart - The daemon auto-uninstalls stale service files that were not created by the current version (tagged with
claude-managed: v1)
Interactive prompt with "Install as a service now? [Y/n/never, or 'once' for this login session]" — search for that string, gated by tengu_quiet_harbor
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_quiet_harbor Off in both readingsThe 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
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.
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.