{"version":"2.1.285","anchor":"settings-repo-tier-freeze-cache","canonical_anchor":"settings-repo-tier-freeze-cache","heading":"Repository-level settings can now be served from a frozen copy","tier":"internal","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/settings-repo-tier-freeze-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Repository-level settings can now be served from a frozen copy\n\nWhen Claude Code loads settings, it can now reuse a frozen copy of a repository's settings instead of reading them again\n\n**Unclear.** It is not clear when settings get frozen.\n\n**What**\n\nClaude Code reads settings from several places, including the repository you are working in. Before reading and checking each place, it now looks for a frozen copy of that place's settings. If one exists, it uses that copy, together with any errors saved with it.\n\n**Why**\n\nRepository-level settings may stay fixed for the length of a session.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}