{"version":"2.1.257","anchor":"new-wire-tool-inputs-field-for-replaying-api-original-tool-i","canonical_anchor":"new-wire-tool-inputs-field-for-replaying-api-original-tool-i","heading":"New wire_tool_inputs field for replaying API-original tool inputs","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-wire-tool-inputs-field-for-replaying-api-original-tool-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New wire_tool_inputs field for replaying API-original tool inputs\n\nAssistant metadata can hold the API's original tool inputs so replayed history echoes calls exactly as emitted.\n\nAssistant message wrapper metadata can now carry a `wire_tool_inputs` field holding the original, API-produced `tool_use` inputs keyed by `tool_use` id, separate from the client-normalized input in `message.content`. This lets replayed conversation history echo tool calls back exactly as the API emitted them.\n\n- Area: Sessions\n- Names: `wire_tool_inputs`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}