tengu_daemon_upgrade_defer_busy
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.248, including the newest one read.
The background service waits for your turn to finish before restarting for an upgrade.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.248.
In the changelogs
5Releases whose published page names tengu_daemon_upgrade_defer_busy.
-
v2.1.300
claude remote-control now rejects --sandbox and --no-sandbox
Passing --sandbox or --no-sandbox to claude remote-control is now an error instead of being silently accepted
gate cited by this entry
-
v2.1.257
GrowthBook feature gates gain a disk cache fallback path in daemon remote control
With no org identity or a failed init, feature gates in the headless daemon serve cached or default values.
gate cited by this entry
-
v2.1.248
The background daemon defers restarts and idle exits while an upgrade is pending
The background service waits for your turn to finish before restarting for an upgrade.
gate cited by this entry, found in this entry's text
-
v2.1.248
Remote-control workers report busy state so upgrades wait for idle
Remote-control upgrades now wait for a worker to go idle instead of cutting sessions off.
gate cited by this entry, found in this entry's text
-
v2.1.248
The background bridge resumes sessions cut off by a restart
The remote-control bridge now re-registers sessions it was running when it restarted.
gate cited by this entry, found in this entry's text
Gate readings
3| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.300 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.257 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.248 | Not enough to say | no value returned | no value returned | on |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
1Build by build
51One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.