{"version":"2.1.277","anchor":"sse-transport-now-surfaces-user-frame-uuids-via-onuserframer","canonical_anchor":"sse-transport-now-surfaces-user-frame-uuids-via-onuserframer","heading":"SSE transport now surfaces user-frame UUIDs via onUserFrameReceived","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/sse-transport-now-surfaces-user-frame-uuids-via-onuserframer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### SSE transport now surfaces user-frame UUIDs via onUserFrameReceived\n\nThe streaming connection now surfaces user-message UUIDs via a new onUserFrameReceived callback\n\n**What**\n\nThe client's SSE (server-sent events) streaming transport now calls a new `onUserFrameReceived(uuid, rawPayload)` callback whenever it receives a frame whose payload type is \"user\" and that carries a string UUID, before it passes the data on to the normal data handler.\n\n**Why**\n\nThis lets other parts of Claude Code react specifically to incoming user-message frames and their identifiers as they stream in, rather than only handling them generically alongside every other frame type.\n\n- Area: Elsewhere\n- Names: `onUserFrameReceived`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}