{"version":"2.1.290","anchor":"permission-checks-use-a-new-input-parser-and-a-new-check-ste","canonical_anchor":"permission-checks-use-a-new-input-parser-and-a-new-check-ste","heading":"Tool permission checks mark requests incomplete when input is set aside","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/permission-checks-use-a-new-input-parser-and-a-new-check-ste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Tool permission checks mark requests incomplete when input is set aside\n\nWhen part of a tool's input is set aside, its permission check is now marked incomplete instead of being allowed outright\n\n**Unclear.** What input gets set aside and what the extra check does are not clear.\n\n**What**\n\nBefore a tool runs, Claude Code reads the tool's input and decides whether it may go ahead. It now reads the input in a way that can set some parts of it aside. When anything was set aside and the decision is not a refusal:\n\n- an allow is turned into a pass-through, which hands the decision on to later steps, and is marked incomplete\n\n- any other result is marked incomplete\n\nAn extra check is also now applied to the result.\n\n**Why**\n\nIn practice, a tool request whose input had parts set aside is no longer approved outright at this step, which could mean more permission prompts.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}