{"version":"2.1.239","anchor":"new-environment-variable-for-what-happens-to-an-unanswered-p","canonical_anchor":"new-environment-variable-for-what-happens-to-an-unanswered-p","heading":"New environment variable for what happens to an unanswered parked permission","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/new-environment-variable-for-what-happens-to-an-unanswered-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### New environment variable for what happens to an unanswered parked permission\n\nCLAUDE_CODE_PARKED_STOP_RETIRES lets you decide the fate of a set-aside permission prompt you never answered.\n\n**What**\n\n`CLAUDE_CODE_PARKED_STOP_RETIRES` joins `CLAUDE_CODE_RETIRE_UNANSWERED_PARKED_PERMISSION` and `CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION` in deciding the fate of a permission prompt that was set aside and never answered. Unset by default, so nothing changes unless you opt in.\n\n**Details**\n\n- A parked permission request is one that was raised but left pending when the turn stopped.\n- The new variable is also consulted when the stop was an interrupt, not just a normal end of turn.\n\n**Evidence**\n\n`CLAUDE_CODE_PARKED_STOP_RETIRES`\n\n- Area: Permissions\n- Names: `CLAUDE_CODE_PARKED_STOP_RETIRES`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}