{"version":"2.1.305","anchor":"bash-ast-too-complex-path-sandbox-override-and-permission-f","canonical_anchor":"bash-ast-too-complex-path-sandbox-override-and-permission-f","heading":"Some commands too complex to analyse no longer always ask for permission","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/bash-ast-too-complex-path-sandbox-override-and-permission-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Some commands too complex to analyse no longer always ask for permission\n\nSome shell commands too complex to analyse can now be allowed by your existing permission rules instead of always prompting\n\n**What**\n\nBefore running a shell command, Claude Code breaks it down to decide whether it is allowed. When a command is too complex to break down, it used to always ask you first.\n\nFor a command that has a keyword after its prefix and no other restrictions, Claude Code now does one of these before falling back to asking:\n\n- checks whether the command asked to run outside the sandbox (the boundary limiting what commands can touch) with `dangerouslyDisableSandbox`\n\n- passes the command on to the normal permission check against your rules\n\n**Why**\n\nSome commands that always prompted before may now be allowed, or blocked, by permission rules you already have.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}