{"version":"2.1.268","anchor":"result-messages-now-get-a-per-session-result-index-stamp","canonical_anchor":"result-messages-now-get-a-per-session-result-index-stamp","heading":"Result messages now get a per-session result_index stamp","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/result-messages-now-get-a-per-session-result-index-stamp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Result messages now get a per-session result_index stamp\n\nResult messages sent over the SDK\/stream-json transport now carry a per-session result_index number\n\n**What**\n\nOutgoing 'result' messages on the SDK and stream-json transport (the machine-readable output formats used by tools and scripts driving Claude Code) now get a `result_index` field, an incrementing number stamped on each message. A tracking mechanism ensures each message only gets stamped once, even if it passes through multiple times.\n\n**Why**\n\nThis gives anything consuming Claude Code's programmatic output a reliable way to tell results apart and put them in order, which is useful for tooling that processes a stream of results rather than reading them one at a time in a terminal.\n\n- Area: SDK\n- Names: `result_index`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}