{"version":"2.1.248","anchor":"refusal-when-a-permission-handler-leaves-nothing-to-send","canonical_anchor":"refusal-when-a-permission-handler-leaves-nothing-to-send","heading":"Refusal when a permission handler leaves nothing to send","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/refusal-when-a-permission-handler-leaves-nothing-to-send","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Refusal when a permission handler leaves nothing to send\n\nIf a permission hook empties a tool call, you now get an explicit failure instead of silence.\n\n**What**\n\nIf a permission hook or handler rewrites a tool call until it is empty, Claude Code now returns an explicit failure explaining that nothing was sent, rather than quietly issuing an empty request.\n\n**Details**\n\n- The message names both the send and subscribe cases.\n\n**Evidence**\n\n`A permission handler rewrote this call so that nothing was left to send or subscribe; nothing was sent.`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}