{"version":"2.1.257","anchor":"wire-format-echo-debugging-fields-tool-inputs-block-order","canonical_anchor":"wire-format-echo-debugging-fields-tool-inputs-block-order","heading":"Wire-format echo debugging fields (tool inputs + block order) are built but flag-gated off","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/wire-format-echo-debugging-fields-tool-inputs-block-order","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Wire-format echo debugging fields (tool inputs + block order) are built but flag-gated off\n\nTwo transcript debugging aids, raw tool inputs and exact wire block order, are computed but each sits behind its own gate.\n\nMessage normalization now computes two extra debugging aids on every pass: a `wire_tool_inputs` field (populated only when the resolved value is a non-empty object, otherwise left `void 0`) attached to tool-call output, and a reordering of assistant content blocks to match exact API wire order before they're written into transcripts\/JSONL. Both are computed unconditionally and fed into the message pipeline, but each is controlled by its own gate function, so neither is active yet.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}