tengu_ccr_orphan_restore_wake
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.247, including the newest one read.
If a container restart kills background work, your session now wakes up and Claude is told what was lost.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.247.
In the changelogs
6Releases whose published page names tengu_ccr_orphan_restore_wake.
-
v2.1.302
Usage data for successful tool calls now includes a hashed call ID
The usage data recorded when a tool call succeeds now includes a scrambled ID for that call, and one restart note builder has been removed
gate cited by this entry
-
v2.1.299
Clearer note to Claude about tool calls lost when a cloud session restarts
After a cloud session restarts, the note telling Claude about lost tool calls can say they are no longer shown and calls unknown tools 'another tool'
gate cited by this entry
-
v2.1.290
Restarted cloud sessions also wake up for timers lost in the restart
After a cloud session restarts, Claude Code now wakes it for lost timers as well as lost background tasks
gate cited by this entry
-
v2.1.285
Waking a resumed remote session for restored background work keeps working the same way
The two settings that decide whether a resumed remote session wakes for restored background agents and shells are still read, both falling back to on
gate cited by this entry, found in this entry's text
-
v2.1.248
Three existing gates relocated, defaults unchanged
Three existing feature gates moved position; their defaults are unchanged.
gate cited by this entry, found in this entry's text
-
v2.1.247
Print mode wakes the session and tells Claude which background work was lost to a container restart
If a container restart kills background work, your session now wakes up and Claude is told what was lost.
gate cited by this entry, found in this entry's text
Gate readings
6| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.302 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.299 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.290 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.285 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 |
| v2.1.247 | 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
52One 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.