Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
In DevelopmentKind: in v2.1.238,
In DevelopmentSection of the release
A listing-based cache cleaner is reachable only under the off-by-default v5 storage decision.
What
The routine that clears out cached plugin binaries now has an alternative that pages through the storage backend's own listing and delete calls instead of scanning directories and file timestamps. It is reached only when the v5 storage decision is on, which is off by default, so in this build every user still gets the old timestamp-scanning cleaner.
Details
The plugin dependency installer passes a storage backend to the cleaner only when the same pin is on; otherwise it passes nothing and the old path runs.
The pin is read once per process from CLAUDE_CODE_HOVER_REST if set, otherwise the tengu_hover_rest flag with a compiled fallback of off. The environment variable is new in this build; the previous release read the flag alone.
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.238: 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.
