Unclear Where the list of lost timers is gathered is not known.
When a remote cloud session restarts, Claude Code already woke it back up to deal with background tasks lost in the restart. It now also wakes it for timers that were lost, and it records how many timers it woke for. Timers here are scheduled things such as repeating loops or wake-ups set for later.
Scheduled loops and wake-ups should no longer be silently lost when a cloud session restarts.
tengu_ccr_orphan_restore_wake Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: on
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.
tengu_ccr_orphan_restore_wake_shells Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: on
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.290. It isn't a statement about your account. What a flag value here can and cannot tell you
Where the list of lost timers is gathered is not known.