{"version":"2.1.288","anchor":"parked-run-config-now-read-as-a-savedserved-object-instead","canonical_anchor":"held-parked-permission-message-hold-open-gate-tengu-polishe","heading":"Parked-run and resume settings reworked, with a new hold-open flag","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/parked-run-config-now-read-as-a-savedserved-object-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Parked-run and resume settings reworked, with a new hold-open flag\n\nSettings for parked and resumed turns now come from saved or served presets, and a new flag tengu_polished_salamander can hold parked messages open\n\n**Unclear.** It is not clear what decides between the two sets or whether the environment variables still affect them.\n\n**What**\n\nWhen 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:\n\n- 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.\n\n- 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.\n\n- The resume settings now include `holdOpenFor`, taken from the message that opened the interrupted turn, which keeps that parked message open.\n\n**Why**\n\nThe 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.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_RESUME_INTERRUPTED_TURN`, `CLAUDE_CODE_PARKED_STOP_RETIRES`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}