You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Headless ModeArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release
What
A 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.
Why
Programs 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.
Read from
Names in the bundlefor_user_message_uuidsclaude -p
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded the date a stored claude.ai sign-in ends to claude auth status (loginExpiresAt) and to claude -p JSON results (credential_expires_at)
