Set an env var so a resumed print session keeps an unanswered permission request still answerable.
What's wrong with this entry?
Setting CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION=1 makes a resumed print/SDK session keep a still-unanswered permission request answerable instead of retiring it. The session comes back in requires_action with the original tool details, the turn is not re-run and the request is not discarded. The variable is a plain boolean with no default, so this is off unless you set it; without it the older CLAUDE_CODE_RETIRE_UNANSWERED_PARKED_PERMISSION behaviour of retiring the request unanswered applies.
- Logs "holding it answerable" and a
tengu_resume_parked_permissionevent withoutcome: held, orheld_supersededif new input arrives while the request is being held. - Control responses that arrive for a different tool use than the held one are dropped with a warning rather than applied.
CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION, CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION); not re-running, not retiring
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 unanswered parked retire
-
v2.1.238
Resumed sessions can adopt a permission prompt left waiting
Both mention hold unanswered parked retire
-
v2.1.239
New environment variable for what happens to an unanswered parked permission
Both mention parked retire