{"version":"2.1.299","anchor":"handoff-validation-allows-repeated-assistant-message-id-for","canonical_anchor":"handoff-validation-allows-repeated-assistant-message-id-for","heading":"Handed-over turns may repeat a message ID only for tool-call continuations","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/handoff-validation-allows-repeated-assistant-message-id-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Handed-over turns may repeat a message ID only for tool-call continuations\n\nA turn handed over to Claude Code may now repeat an assistant message ID only when the next message is tool calls alone\n\n**What**\n\nClaude Code checks a turn that is handed over to it from a server before using it. A repeated assistant message ID is now allowed in one case only: in the next assistant message, when that message contains nothing but tool calls (requests to run tools) and only tool results come between. Any other repeat is rejected with the error `message_id_repeats`. Before, any repeat or already-seen message was rejected with a single error.\n\nThe description of safety check results now says that, for a repeated message ID, only a verdict that flags the call is used.\n\n**Why**\n\nThis affects turns that a server hands over to Claude Code to continue.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}