{"version":"2.1.314","anchor":"malformed-tool-use-exhausted-termination-reason","canonical_anchor":"malformed-tool-use-exhausted-termination-reason","heading":"A separate stop reason for repeated malformed tool calls","tier":"notice","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/malformed-tool-use-exhausted-termination-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### A separate stop reason for repeated malformed tool calls\n\nClaude Code can now report malformed_tool_use_exhausted as the reason a run stopped, for a case it did not single out before\n\n**Unclear.** The exact condition that ends a run with this reason is not stated.\n\n**What**\n\nWhen Claude Code reports why a run ended, it can now give the reason `malformed_tool_use_exhausted`. A tool call is a request from the model to use one of Claude Code's tools, such as reading a file. A malformed one is a request that is badly formed and cannot be carried out. This reason covers a case that was not reported separately before.\n\n**Why**\n\nIt points to a distinct stop reason for when the model keeps producing tool calls that cannot be used, so a run that ends this way can be told apart from other endings.\n\n- Area: Headless Mode\n- Names: `malformed_tool_use_exhausted`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}