{"version":"2.1.317","anchor":"parked-permission-adoption-skipped-for-strict-answers","canonical_anchor":"parked-permission-adoption-skipped-for-strict-answers","heading":"Resumed sessions with strict answers no longer take over a waiting permission request","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/parked-permission-adoption-skipped-for-strict-answers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resumed sessions with strict answers no longer take over a waiting permission request\n\nWhen a session resumes, a permission request that was set aside is now taken over only if the session's answers are not set to strict\n\n**What**\n\nA permission request is Claude Code asking for approval before Claude does something. A request can be parked, meaning it is set aside while it still waits for an answer.\n\nBefore, when a session was resumed, Claude Code took over a parked request whenever there was one. Now it does so only when the session's way of handling answers is not set to strict.\n\n**Why**\n\nThis changes what a resumed session does with a permission question that was still waiting when the session stopped.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}