You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.282,
What probably matters to youSection of the release
What
The SDK lets other programs, such as a desktop app, run Claude Code and receive its messages as a stream. This release adds a new kind of system message on that stream:
It is a system message with subtype session_metadata, carrying metadata.artifacts. Each artifact has a url, title, favicon, kind "frame" and updated_at, and the list becomes null once it is empty. Its description says it mirrors the external_metadata update a cloud worker sends, so an SDK host can keep the per-session summary a cloud session gets without reading transcript rows.
The SDK stream loop now forwards these messages, alongside post_turn_summary and task_summary.
The WebSocket remote-session client filters them out, so they do not appear as conversation messages.
Why
Local SDK hosts can now track a session's published artifacts the way cloud sessions already do. If you consume the SDK stream, expect session_metadata messages you did not receive before.
Read from
Names in the bundlesession_metadata
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhen Claude Code actually sends this message is not known.
