{"version":"2.1.312","anchor":"message-removal-now-goes-through-an-in-turn-recorder-and-awa","canonical_anchor":"message-removal-now-goes-through-an-in-turn-recorder-and-awa","heading":"Removing a message now waits until the transcript has been written","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/message-removal-now-goes-through-an-in-turn-recorder-and-awa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Removing a message now waits until the transcript has been written\n\nWhen Claude Code removes a message from a session, it now records the removal as part of the turn and waits for it to be saved\n\n**What**\n\nThe transcript is the saved record of a session. When Claude Code removes a message from it, the removal is now recorded as part of the current turn. Claude Code also waits until pending changes have been written before it carries on.\n\n**Why**\n\nThis may keep the transcript's writes in the right order, so a removal does not land before or after the wrong message.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}