{"version":"2.1.238","anchor":"a-second-plugin-asset-cache-cleaner-exists-switched-off-in-t","canonical_anchor":"a-second-plugin-asset-cache-cleaner-exists-switched-off-in-t","heading":"A second plugin asset-cache cleaner exists, switched off in this build","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/a-second-plugin-asset-cache-cleaner-exists-switched-off-in-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### A second plugin asset-cache cleaner exists, switched off in this build\n\nAn alternative plugin cache cleaner exists, but you still get the old file-timestamp scan.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- 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.\n- 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.\n\n**Evidence**\n\n`tengu_hover_rest served a `\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.238; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Plugins\n- Names: `CLAUDE_CODE_HOVER_REST`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}