Group of 2 Under the hood
Whether Claude Code resumes an interrupted turn is now configurable per call and read from a lane config object instead of only an env var
What
Behavior around resuming an interrupted turn, previously controlled only by the CLAUDE_CODE_RESUME_INTERRUPTED_TURN environment variable, changed in two ways:
- The message-deserialization/resume function gained a fifth parameter that, when provided, overrides the
CLAUDE_CODE_RESUME_INTERRUPTED_TURNcheck for that specific call instead of always reading the environment variable directly. - More broadly, this and related behaviors — resuming interrupted turns, holding unanswered parked permissions, retiring parked stops, and tolerating context appends on resume — now read from a
this.laneconfig object (resumeInterruptedTurn,holdUnanswered,parkedStopRetires,toleratesContextAppends) instead of directly from theCLAUDE_CODE_RESUME_INTERRUPTED_TURN,CLAUDE_CODE_HOLD_UNANSWERED_PARKED_PERMISSION,CLAUDE_CODE_PARKED_STOP_RETIRES, andCLAUDE_CODE_RESUME_TOLERATES_CONTEXT_APPENDSenvironment variables.
Why
Moving these settings into a lane config object, with the option to override per call, allows resume-related behavior to be controlled more flexibly than a fixed environment variable read for the whole process.
Names in the bundleCLAUDE_CODE_RESUME_INTERRUPTED_TURN
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up CLAUDE_CODE_RESUME_INTERRUPTED_TURN, on Claude Code changelog.
* Fixed a local `claude -p --resume` started with `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` not reporting background tasks the previous process left unfinishedchangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up CLAUDE_CODE_RESUME_INTERRUPTED_TURN, on Claude Code changelog.