An alternative plugin cache cleaner exists, but you still get the old file-timestamp scan.
A listing-based cache cleaner is reachable only under the off-by-default v5 storage decision.
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.238: on
Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
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.
- 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_RESTif set, otherwise thetengu_hover_restflag with a compiled fallback of off. The environment variable is new in this build; the previous release read the flag alone.
tengu_hover_rest served a
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Precomputed session resolution on resume, gated off
Both mention hover rest
-
v2.1.234
Resume reads the pre-compaction sidecar ahead of time
Both mention hover rest
-
v2.1.242
On-disk storage layer gains symlink and permission rules per data type
Both mention hover rest