{"version":"2.1.238","anchor":"plaintext-credential-store-gained-an-in-process-cache","canonical_anchor":"plaintext-credential-store-gained-an-in-process-cache","heading":"Plaintext credential store gained an in-process cache","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/plaintext-credential-store-gained-an-in-process-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Plaintext credential store gained an in-process cache\n\nPlaintext credential reads could come from memory instead of the file, but only under off-by-default storage.\n\n**What**\n\nReads of the plaintext credential store can be served from a cached snapshot held in memory rather than re-reading the file, with a generation counter and an explicit invalidation entry point. Every write, delete and failed read clears it. This only applies when the off-by-default v5 storage decision is on.\n\n**Details**\n\n- Controlled by the same latched pin as the rest of v5 storage: `CLAUDE_CODE_HOVER_REST` if set, otherwise `tengu_hover_rest`, whose fallback is off.\n\n**Evidence**\n\n`fromStoreCopy`\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: Internals\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"}