A complete in-memory version of the new v5 storage backend now ships as its own chunk: a tree of directory, value and stream nodes with appends, tombstones, record replacement, leases, change subscriptions, scope listing and deletion, and per-log-channel byte budgets. Whether any of it is used depends on the CLAUDE_CODE_HOVER_REST environment variable, or otherwise the tengu_hover_rest flag, whose compiled fallback is off.
Details
Versions are strings shaped s<epoch>.<generation>.<seq>.
Construction is wrapped in a guard that reports success or a fell_back outcome and, on failure, drops back to the legacy storage path.
Evidence
v5 in-memory storage backend construction failed; this worker keeps no storage backend
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The 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.248: off
Flag reading movedThe flag server now returns off for tengu_hover_rest, read as this 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.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_hover_rest, read as this 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.
