{"version":"2.1.257","anchor":"new-echoapiblockorder-mode-preserves-original-api-block-or","canonical_anchor":"new-echoapiblockorder-mode-preserves-original-api-block-or","heading":"New echoWireToolInputs and echoApiBlockOrder options preserve raw wire data across merges and compaction","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-echoapiblockorder-mode-preserves-original-api-block-or","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New echoWireToolInputs and echoApiBlockOrder options preserve raw wire data across merges and compaction\n\nMerged assistant messages can preserve the API's original content block ordering rather than concatenating.\n\nAssistant message merging (`ets`) gained an alternate path that, when `echoApiBlockOrder` is true and both messages carry an `apiBlockIndex`, merges content blocks by their original API index order instead of simple concatenation, threading `apiBlockIndices` through the message.\n\nTranscript compaction now supports the same `echoApiBlockOrder` option plus a new `echoWireToolInputs` option; when set, these preserve raw wire tool inputs (`wireToolInputs`) and original API block ordering (`apiBlockIndex`\/`apiBlockIndices`) instead of normalizing them, likely for diagnostics or exact-replay of assistant tool calls.\n\n- Area: Sessions\n- Names: `echoApiBlockOrder`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}