{"version":"2.1.309","anchor":"tool-input-repair-errors-now-name-the-failing-stage-without","canonical_anchor":"tool-input-repair-errors-now-name-the-failing-stage-without","heading":"Tool input errors are logged by stage, without their text","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/tool-input-repair-errors-now-name-the-failing-stage-without","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Tool input errors are logged by stage, without their text\n\nWhen fixing up a tool's streamed input fails, Claude Code now logs which step failed instead of the error text\n\n**What**\n\nWhile Claude writes a reply, the input for a tool call (one action Claude takes) arrives in pieces, and Claude Code repairs and tidies that input before using it. When this fails with an error other than a normal input check failure, Claude Code now logs which step failed: the repair step or the tidying step. The text of the error is no longer logged. In earlier builds the raw error text was logged.\n\n**Why**\n\nError text can contain parts of what you were working on. Logging only the step that failed keeps that content out of the diagnostics.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}