{"version":"2.1.268","anchor":"new-num-turns-adjacent-seq-field-documented-for-stream-jso","canonical_anchor":"new-num-turns-adjacent-seq-field-documented-for-stream-jso","heading":"New num_turns-adjacent 'seq' field documented for stream-json results","tier":"use","area":"Stream JSON","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-num-turns-adjacent-seq-field-documented-for-stream-jso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New num_turns-adjacent 'seq' field documented for stream-json results\n\nStream-json results from claude -p now document a 'seq' delivery-order field\n\n**What**\n\nResults returned in stream-json format (used with `claude -p`) now have a documented `seq` field, a delivery sequence number counting how many results the run has numbered before this one, starting at 0. It counts in the order results are written, not the order they were produced, and it still increments even if a particular write fails, so a gap in the sequence means a result was lost. This field is absent from the in-process engine surface and from error results built locally by cloud-relay clients.\n\n**Why**\n\nThis gives consumers of stream-json output a way to detect whether any results were dropped in transit, by watching for gaps in the sequence numbers.\n\n- Area: Stream JSON\n- Names: `seq`, `claude -p`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}