{"version":"2.1.300","anchor":"unanswered-permission-requests-now-tell-the-model-to-stop-re","canonical_anchor":"unanswered-permission-requests-now-tell-the-model-to-stop-re","heading":"Claude stops retrying when a permission request goes unanswered","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/unanswered-permission-requests-now-tell-the-model-to-stop-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Claude stops retrying when a permission request goes unanswered\n\nAfter a permission request gets no answer, Claude is told you may be away, to stop asking, finish what it can, and then say what it needed\n\n**Unclear.** Which modes or sessions give Claude this instruction is not stated.\n\n**What**\n\nSome actions need your approval before Claude can take them. Claude Code now has an instruction for when such a request gets no answer. It tells Claude:\n\n- You may be away, so further requests are likely to go unanswered too\n\n- Not to retry the action, and not to try other actions that need approval, until you write again\n\n- To finish the work that needs no approval\n\n- Then to say what it needed approval for\n\n**Why**\n\nWhen nobody is there to approve, Claude does not keep stacking up requests. You come back to the finished part of the work and a list of what still needs your OK.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}