{"version":"2.1.288","anchor":"send-now-interrupts-are-stamped-so-later-messages-can-be-att","canonical_anchor":"send-now-interrupts-are-stamped-so-later-messages-can-be-att","heading":"Messages sent to interrupt Claude are now tracked in the transcript","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/send-now-interrupts-are-stamped-so-later-messages-can-be-att","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Messages sent to interrupt Claude are now tracked in the transcript\n\nSending a message that interrupts Claude now only stops a turn that is still running, and later transcript messages are marked as following that cut\n\n**Unclear.** It is not clear whether the new marking changes anything you can see in the transcript.\n\n**What**\n\nYou can send a message that interrupts Claude while it is still working on a turn, which is one round of Claude responding. Claude Code now only stops the turn if it has not already been stopped. It also remembers that the interruption happened, and messages written to the transcript afterwards are marked as coming after that cut. Before, sending such a message simply stopped the turn with nothing recorded.\n\n**Why**\n\nThis changes how interrupted turns are recorded in the transcript, the saved history of the conversation, so it is clearer which messages came after you cut in.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}