CLAUDE_CODE_PARKED_STOP_RETIRES lets you decide the fate of a set-aside permission prompt you never answered.
What's wrong with this entry?
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.
- A parked permission request is one that was raised but left pending when the turn stopped.
- The new variable is also consulted when the stop was an interrupt, not just a normal end of turn.
CLAUDE_CODE_PARKED_STOP_RETIRES
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.233
Env var to drop permission prompts left unanswered when a session resumes
Both mention parked retire
-
v2.1.235
Unanswered permission prompts can be held open across a resume
Both mention parked retire
-
v2.1.227
claude rmtells you which session is holding a directoryBoth mention stop