{"version":"2.1.282","anchor":"stub-hookpermission-source-for-settings-is-compiled-out","canonical_anchor":"stub-hookpermission-source-for-settings-is-compiled-out","heading":"Groundwork for another settings source for hooks and allow rules, not active","tier":"soon","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/stub-hookpermission-source-for-settings-is-compiled-out","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Groundwork for another settings source for hooks and allow rules, not active\n\nClaude Code now checks for one more settings source for hooks and allow rules, but in this build that check always adds nothing\n\n**What**\n\nWhen Claude Code gathers hooks (your own commands that run at set moments) and allow rules (permissions you have granted in advance), it reads `.claude\/settings.json` and `.claude\/settings.local.json`. It now also asks for one further settings source. In this build that request always comes back empty, so nothing is added.\n\n**Why**\n\nThis has no effect today. It points to an extra place for settings that is still being built.\n\n- Area: Settings\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}