Unclear What triggers the storage-backed path versus the filesystem fallback in practice is not specified.
Asciicast recordings gain a storage-backed path under storage v5, keyed by a recording namespace that includes project, session, and timestamp. Listing recordings now merges on-disk .cast files with entries held in this storage namespace, and renaming a recording can go through a parked callback registered on the recorder rather than a direct filesystem rename.
The previous behavior, renaming the file directly to <sessionId>-<timestamp>.cast, remains as a fallback.
tengu_hover_rest 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.235: off
Read once, for one account on one subscription tier, against v2.1.235. 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.
What triggers the storage-backed path versus the filesystem fallback in practice is not specified.