{"version":"2.1.319","anchor":"new-managed-permission-setting-denyinsteadofprompting","canonical_anchor":"new-managed-permission-setting-denyinsteadofprompting","heading":"New permission setting denyInsteadOfPrompting is carried through settings","tier":"use","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/new-managed-permission-setting-denyinsteadofprompting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### New permission setting `denyInsteadOfPrompting` is carried through settings\n\nClaude Code now passes along a `permissions.denyInsteadOfPrompting` setting when it is set to true, next to the read and write block settings\n\n**Unclear.** What this setting does once set, and which settings files it is read from, is not confirmed.\n\n**What**\n\nWhen Claude Code combines settings from different places, it now carries over `permissions.denyInsteadOfPrompting` when it is set to true. It is handled alongside `blockReadsOutsideWorkingDirectories` and `blockWritesOutsideWorkingDirectories`, which stop Claude Code reading or writing outside your working folders.\n\n**Why**\n\nThe name suggests a way to refuse actions instead of asking you about them, which could matter for unattended or centrally managed setups that want no prompts.\n\n- Area: Permissions\n- Names: `permissions.denyInsteadOfPrompting`, `blockReadsOutsideWorkingDirectories`, `blockWritesOutsideWorkingDirectories`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}