{"version":"2.1.323","anchor":"restart-orphaned-permission-approvals-are-denied-with-an-exp","canonical_anchor":"restart-orphaned-permission-approvals-are-denied-with-an-exp","heading":"Permission requests left over from before a restart are now refused with a clear reason","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/restart-orphaned-permission-approvals-are-denied-with-an-exp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Permission requests left over from before a restart are now refused with a clear reason\n\nA permission request asked before Claude Code restarted is refused, and Claude is told to call the tool again\n\n**What**\n\nSome actions Claude takes need your approval first. That approval is called a permission. If Claude Code asked for one and then restarted before you answered, the old request is now refused with an explicit message. The message says the approval cannot be reused and tells Claude to call the tool again with the same arguments, since it may need your approval again.\n\nA request that was cancelled gets the message \"Tool permission request aborted\".\n\n**Why**\n\nAfter you resume a session, an out-of-date approval is no longer silently reused and does not leave things waiting. Claude retries the action, and you may be asked to approve it again.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}