Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.281entry #91

Claude Code v2.1.281 ·

SDK conversation_reset messages say what caused the reset

The SDK conversation_reset message gains optional trigger, user_message_uuid and timestamp fields, and ultraplan's fresh-session flow sets its trigger

Group of 2 Use it now Internal Changes
JSON All of v2.1.281
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.281,
What probably matters to youSection of the release

What

The SDK (the kit developers use to build their own programs on top of Claude Code) sends a conversation_reset message whenever the current conversation is thrown away. That message now has three new optional fields:

  • trigger says what discarded the conversation: clear, plan_mode_exit, fresh_session or onboarding. clear means the /clear command or its aliases /reset and /new.
  • user_message_uuid lets a program match the reset to the /clear message it has already seen.
  • timestamp is an ISO time that can be shown to the user.

The description of the message now also lists onboarding re-runs as a cause. The ultraplan flow that implements a plan "in a fresh session" now marks its reset as fresh_session.

Why

Programs built on the SDK, and Remote Control clients, can now tell why a conversation was reset. They can also clear a transcript exactly once, even when the related messages arrive out of order.

See this entry in the whole of v2.1.281 →

Feedback