{"version":"2.1.312","anchor":"tengu-vast-journal-telemetry-gate-call-removed-from-the-resu","canonical_anchor":"tengu-vast-journal-telemetry-gate-call-removed-from-the-resu","heading":"Resuming an interrupted turn no longer depends on a server switch for one check","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/tengu-vast-journal-telemetry-gate-call-removed-from-the-resu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Resuming an interrupted turn no longer depends on a server switch for one check\n\nOne part of the check that decides whether an interrupted turn can be resumed no longer consults a server-side switch\n\n**Unclear.** It is not clear which part of resuming an interrupted turn the removed switch controlled.\n\n**What**\n\nWhen you resume a session whose last turn was interrupted, Claude Code runs several checks to decide how to treat that turn. One of those checks also used to ask a server-side switch, a setting Anthropic can turn on or off remotely, before it could pass. That switch is no longer consulted. The check now depends only on what the session's messages contain.\n\nIn the previous release, that switch was on by default when the server sent nothing.\n\n**Why**\n\nThe switch appears to have been retired. Whichever sessions this check covers now follow the same path every time, rather than one Anthropic could change remotely.\n\n- Flag `tengu_vast_journal`: Not enough to say (read for one account on one subscription tier against v2.1.312; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}