Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.236,
What probably matters to youSection of the release
What
The newer v5 session-storage backend used to be consulted wherever a caller happened to check tengu_hover_rest or simply passed a v5 handle. This build reads the flag once at startup and pins the answer, and every v5 path now checks the pinned value too: session file writes, plugin listing, sidecar writes, session-metadata re-append, config backup listing, and skill and plugin existence checks. Passing a v5 handle is no longer enough, and the choice cannot flip mid-session.
Details
The flag falls back to false, so it is off unless remote config turns it on.
A later read that disagrees with the pinned value logs a warning and keeps the original decision.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_hover_restOff in both readings
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.236: 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.
