{"version":"2.1.288","anchor":"permission-check-gains-early-return-helper-and-crashisobject","canonical_anchor":"permission-check-gains-early-return-helper-and-crashisobject","heading":"A crashing permission check can ask you instead of letting the action through","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/permission-check-gains-early-return-helper-and-crashisobject","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### A crashing permission check can ask you instead of letting the action through\n\nWhen a permission check fails with an error and a certain option is set, Claude Code asks for your approval instead of passing the action on\n\n**Unclear.** What sets this option is not stated, so it is unclear when it applies.\n\n**What**\n\nClaude uses tools to take actions, such as running a command or editing a file. Before each tool call, Claude Code checks whether the action is allowed.\n\nThat permission check now runs an early step first and returns its answer if it gives one. A check can also fail with an error. When that happens and an option that treats such failures as objections is set, Claude Code asks you what to do. Before, the action was passed on with the check marked as incomplete.\n\n**Why**\n\nA broken check can lead to a prompt instead of an action going through without a full check.\n\n- Flag `tengu_mcp_server_policy_bypass_exempt`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}