{"version":"2.1.236","anchor":"remote-settings-caching-watches-a-second-file-and-skips-redu","canonical_anchor":"remote-settings-caching-watches-a-second-file-and-skips-redu","heading":"Remote settings caching watches a second file and skips redundant priming","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/remote-settings-caching-watches-a-second-file-and-skips-redu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Remote settings caching watches a second file and skips redundant priming\n\nCached remote settings now come with a companion attestation file, and both must load cleanly.\n\n**What**\n\nThe component that reads cached remote settings from disk now tracks two files rather than one, the cache itself and a companion file whose contents become an attestation string, reading the companion only after the cache and standing the whole view down if either read fails or is oversized.\n\n**Details**\n\n- Priming is now skipped when a cache was already loaded this session, joining the existing skip reasons of ineligibility and the `CLAUDE_CODE_REMOTE_SETTINGS_PATH` override.\n- The prime log line now reports whether the companion attestation was present.\n- Applies only on the newer storage path; no new flag. Visible only in debug logs.\n\n**Evidence**\n\n`helper consent sidecar`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}