{"version":"2.1.305","anchor":"orphaned-permission-handoff-gets-disallowedtools-and-personw","canonical_anchor":"orphaned-permission-handoff-gets-disallowedtools-and-personw","heading":"Handed-off permission prompts keep your blocked-tool list","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/orphaned-permission-handoff-gets-disallowedtools-and-personw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Handed-off permission prompts keep your blocked-tool list\n\nA turn handed off after its permission prompt was left unanswered now carries the session's `disallowedTools` list, replacing any other\n\n**What**\n\nA turn can stop at a permission prompt, where Claude asks whether it may use a tool, and that prompt can be left with nobody to answer it. When such a turn is handed off to carry on, it now takes the `disallowedTools` list with it. That is the list of tools Claude is not allowed to use, and it replaces any list the receiving side already had rather than adding to it.\n\nWhen the handed-off message was written by a person, Claude Code also now records it as a person's message.\n\n**Why**\n\nA resumed turn keeps the same tool restrictions as the session it came from, so a tool you blocked stays blocked.\n\n- Area: Permissions\n- Names: `disallowedTools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}