{"version":"2.1.293","anchor":"input-transformations-stripped-from-streamed-message-events","canonical_anchor":"input-transformations-stripped-from-streamed-message-events","heading":"Streamed responses no longer pass on the input_transformations field","tier":"internal","area":"API Client","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/input-transformations-stripped-from-streamed-message-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Streamed responses no longer pass on the input_transformations field\n\nClaude Code now removes a field called input_transformations from streamed message events before passing them on\n\n**Unclear.** It is not clear whether this changes the streamed output that people reading Claude Code's own output can see.\n\n**What**\n\nWhen Claude's reply arrives as a stream (sent piece by piece instead of all at once), Claude Code now removes a field called `input_transformations` from two kinds of event before passing them on:\n\n- the event that opens a new message\n\n- the events that update a message while it is being written\n\nThe field name was already known to Claude Code. What is different is that it is now stripped out.\n\n**Why**\n\nAnything further along that reads these streamed events will no longer see this field.\n\n- Area: API Client\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}