{"version":"2.1.312","anchor":"sandbox-permission-checks-drop-permissionmode-argument","canonical_anchor":"sandbox-permission-checks-drop-permissionmode-argument","heading":"A restricted sandbox permission check no longer receives the permission mode","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/sandbox-permission-checks-drop-permissionmode-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### A restricted sandbox permission check no longer receives the permission mode\n\nOne restricted permission check used with the sandbox no longer passes along your current permission mode\n\n**Unclear.** It is not stated how, or whether, permission decisions differ as a result.\n\n**What**\n\nThe sandbox is a fenced-off area that limits what commands Claude runs can touch. When Claude Code falls back to a restricted permission check, it used to pass along your current permission mode, the setting that controls how much Claude may do without asking. It now passes only the fact that the check is restricted.\n\n**Why**\n\nThe outcome of this check may no longer depend on which permission mode you are in.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}