{"version":"2.1.319","anchor":"avoid-prompts-mode-now-marks-avoidspromptsbynature-denyinst","canonical_anchor":"avoid-prompts-mode-now-marks-avoidspromptsbynature-denyinst","heading":"No-prompt permission mode and denyInsteadOfPrompting are treated differently","tier":"notice","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/avoid-prompts-mode-now-marks-avoidspromptsbynature-denyinst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### No-prompt permission mode and denyInsteadOfPrompting are treated differently\n\nThe mode that avoids permission prompts now marks itself as avoiding them by nature, and `denyInsteadOfPrompting` now counts as a restrictive setting\n\n**Unclear.** What either change does to which actions are allowed, denied or asked about.\n\n**What**\n\nA permission prompt is when Claude Code stops to ask you whether it may do something. Two changes affect how Claude Code handles these when no one is there to answer:\n\n- No-prompt mode: the mode that avoids permission prompts now also marks itself as avoiding them by nature.\n\n- `denyInsteadOfPrompting`: this setting is now checked alongside `blockReadsOutsideWorkingDirectories` and `blockWritesOutsideWorkingDirectories` as a restrictive setting.\n\n**Why**\n\nThis may change how permission prompts are handled when Claude Code runs without a person at the keyboard.\n\n- Area: Permissions\n- Names: `permissions.denyInsteadOfPrompting`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}