Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Parked-run and resume settings reworked, with a new hold-open flag

Settings for parked and resumed turns now come from saved or served presets, and a new flag tengu_polished_salamander can hold parked messages open

Group of 2 Nothing to try yet Internal Changes
JSON All of v2.1.288
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.288,
In DevelopmentSection of the release

Unclear It is not clear what decides between the two sets or whether the environment variables still affect them.

What

When a background session's turn is interrupted or paused waiting for a permission answer, Claude Code "parks" it and can resume it later. The settings for this behaviour have changed:

  • The settings (such as resumeInterruptedTurn, adoptUnderivable and parkedStopRetires) used to be built by reading environment variables like CLAUDE_CODE_RESUME_INTERRUPTED_TURN and CLAUDE_CODE_PARKED_STOP_RETIRES directly, plus answerWaitMs. They are now taken from one of two prepared sets, a saved one or a served one. The environment variable names still appear in the code, so they are probably read elsewhere.
  • A new flag, tengu_polished_salamander, is read as the value 'on' to decide whether a parked permission message is held open (holdsParkedMessageOpen). The flag server returned off for this site's account and on for an anonymous check, but no reading has been taken under this release yet.
  • The resume settings now include holdOpenFor, taken from the message that opened the interrupted turn, which keeps that parked message open.

Why

The defaults for parking and resuming may now come from these prepared sets rather than from environment variables you set, so check how they behave if you rely on those variables.

Read from
Since it was published

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 `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` re-running a finished turn after a restart when an MCP tool result had ended that turn changelog see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what decides between the two sets or whether the environment variables still affect them.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CODE_RESUME_INTERRUPTED_TURN, on Claude Code changelog.

See this entry in the whole of v2.1.288 →

Feedback