{"version":"2.1.293","anchor":"local-settings-location-cached-for-settings-reach-check","canonical_anchor":"local-settings-location-cached-for-settings-reach-check","heading":"Local settings file location is now remembered during a settings check","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/local-settings-location-cached-for-settings-reach-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Local settings file location is now remembered during a settings check\n\nClaude Code now stores where your local settings file is and its resolved real location, instead of working out the real location each time\n\n**What**\n\nClaude Code has a check that decides whether a settings change reaches your local settings file, the per-project settings file kept on your own machine. That check now remembers two things about the file: the path as it is written, and its real location on disk once any links are followed. It uses both to decide whether a change reaches the file. Before, it worked out the real location again each time.\n\n**Why**\n\nThis check is part of how Claude Code asks for consent before running hooks set up on your device. A hook is a command you configure to run automatically at set points while Claude Code works. No visible change is known.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}