{"version":"2.1.290","anchor":"drop-trailing-api-error-notice-when-it-is-followed-by-tool-u","canonical_anchor":"drop-trailing-api-error-notice-when-it-is-followed-by-tool-u","heading":"A stray API error at the end of a result can now be dropped","tier":"notice","area":"API Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/drop-trailing-api-error-notice-when-it-is-followed-by-tool-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A stray API error at the end of a result can now be dropped\n\nClaude Code can now discard a trailing API error before giving its final result, ending the turn as a tool use\n\n**Unclear.** The exact condition that makes Claude Code drop the error is not known.\n\n**What**\n\nBefore giving its final result, Claude Code can now throw away an API error that sits at the very end. An API error is a failed reply from Anthropic's servers. When it drops one, it clears the error state and reports the turn as ending with a tool use (`tool_use`) instead.\n\n**Why**\n\nPrograms using Claude Code without its interface, through the SDK (the toolkit for driving Claude Code from code) or headless mode, should see fewer false error results.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}