{"version":"2.1.292","anchor":"tool-input-coercion-no-longer-depends-on-coerceinputbeforepl","canonical_anchor":"tool-input-coercion-no-longer-depends-on-coerceinputbeforepl","heading":"Badly formed tool inputs are repaired in more cases","tier":"notice","area":"Tool Calls","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/tool-input-coercion-no-longer-depends-on-coerceinputbeforepl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Badly formed tool inputs are repaired in more cases\n\nClaude Code now tries to repair invalid tool input whenever a tool has a repair step, and keeps the original input alongside the fix\n\n**What**\n\nWhen Claude uses a tool (an action such as reading a file or running a command), it sends the tool some input. Some tools have a built-in step that tries to fix input that is not in the expected shape. That step now runs whenever the tool has one and the input fails the check. Before, it only ran for tools that had also opted in to running it ahead of plugin hooks.\n\nThe record of each repair now also keeps the original input as it was sent.\n\n**Why**\n\nMore malformed tool inputs get fixed instead of failing, and the original input is still there if something needs to be reported.\n\n- Area: Tool Calls\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}