{"version":"2.1.273","anchor":"new-marker-based-transcript-relayhand-off-refusal-codes-and","canonical_anchor":"new-marker-based-transcript-relayhand-off-refusal-codes-and","heading":"New marker-based transcript relay\/hand-off refusal codes and checks for cross-version updates","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-marker-based-transcript-relayhand-off-refusal-codes-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New marker-based transcript relay\/hand-off refusal codes and checks for cross-version updates\n\nThe mechanism that hands off a session transcript during \/update now has more precise failure checks\n\n**What**\n\nClaude Code has an internal relay mechanism, using markers embedded in a transcript, that hands off session state (including prompt cache data) during an `\/update`. It now has specific, named refusal reasons for when this hand-off can't proceed, such as a marker not being in an inactive state, a missing marker line, an unexpected marker line format, or an anchor point not being in view. It also now checks that a \"thinking strip\" isn't owed, and checks that the resuming session hasn't already answered a turn of its own before arming the relay.\n\n**Why**\n\nThese added checks make the hand-off between old and new versions during an update more reliable, catching mismatched or stale states before they cause problems rather than after.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}