{"version":"2.1.268","anchor":"transport-now-tracks-resultdelivery-for-numbered-results","canonical_anchor":"transport-now-tracks-resultdelivery-for-numbered-results","heading":"Transport now tracks resultDelivery for numbered results","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/transport-now-tracks-resultdelivery-for-numbered-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Transport now tracks resultDelivery for numbered results\n\nSession transport now tracks a resultDelivery object so 'result' messages can be numbered\n\n**Unclear.** What actually consumes the numbered results, and why numbering was needed, isn't shown in the evidence.\n\n**What**\n\nAt startup, Claude Code now wires a new `resultDelivery` object onto the session's transport layer. It's used to stamp outgoing 'result' type messages so they can be delivered with a sequence number, and a separate counter reads that number back off `resultDelivery` elsewhere.\n\n**Why**\n\nNumbering result messages likely helps consumers of the session transport track ordering or detect gaps in delivered results, though the evidence doesn't spell out the specific consumer.\n\n- Area: SDK\n- Names: `resultDelivery`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}