Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial

New CLAUDE_CODE_PARKED_PERMISSION_WAIT_MS env var sets a 2 second default wait for parked permissions

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPermissionswhat it touches
KindNew Featuresin v2.1.275,
Use it now Notable

New CLAUDE_CODE_PARKED_PERMISSION_WAIT_MS env var sets a 2 second default wait for parked permissions

What

A new environment variable, CLAUDE_CODE_PARKED_PERMISSION_WAIT_MS, controls a wait time used in logic around "parked" permissions and resuming a turn. If it isn't set, it defaults to 2000 milliseconds (2 seconds). It appears alongside other related environment variables: CLAUDE_CODE_RESUME_INTERRUPTED_TURN, CLAUDE_CODE_ADOPT_UNDERIVABLE_PARKED_PERMISSION, and CLAUDE_CODE_PARKED_STOP_RETIRES.

Why

This gives more control over timing in the logic that resumes interrupted turns and handles permission requests that were left pending ('parked'), building on the existing CLAUDE_CODE_RESUME_INTERRUPTED_TURN recovery behavior, which was previously narrowed to remote sessions and fixed to report unfinished background tasks after a local claude -p --resume.

Read from
Names in the bundleCLAUDE_CODE_PARKED_PERMISSION_WAIT_MSCLAUDE_CODE_RESUME_INTERRUPTED_TURNCLAUDE_CODE_ADOPT_UNDERIVABLE_PARKED_PERMISSIONCLAUDE_CODE_PARKED_STOP_RETIRES
What the documentation says
CLAUDE_CODE_RESUME_INTERRUPTED_TURN Claude Code changelog modified, high confidence * Fixed a local `claude -p --resume` started with `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` not reporting background tasks the previous process left unfinished see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesCLAUDE_CODE_RESUME_INTERRUPTED_TURN on Claude Code changelog
Anthropic's release notes agreeFixed --resume, the resume picker preview, resumed background agents and the transcript view failing on a session whose saved history…

See this entry in the whole of v2.1.275 →