{"version":"2.1.318","anchor":"stop-message-uuid-description-extended-to-claude-p","canonical_anchor":"stop-message-uuid-description-extended-to-claude-p","heading":"A targeted Stop in claude -p also spares messages read but not yet queued","tier":"notice","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/stop-message-uuid-description-extended-to-claude-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A targeted Stop in claude -p also spares messages read but not yet queued\n\nIn claude -p, a Stop that names messages Claude Code has read but not yet queued no longer interrupts the current turn\n\n**What**\n\nA Stop request can list, in `for_user_message_uuids`, the messages it is meant to interrupt. The description of that field now covers one more case. In `claude -p`, the non-interactive print mode, a Stop that names a message Claude Code has already read but not yet put in its queue also leaves the current turn running. Before, only a Stop naming already queued work was spared in this way.\n\n**Why**\n\nPrograms that drive Claude Code in print mode can send a Stop for a message that has only just arrived without cancelling the turn Claude is working on.\n\n- Area: Headless Mode\n- Names: `for_user_message_uuids`, `claude -p`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}