{"version":"2.1.199","anchor":"agent-api-error-recovery-partial-output-surfaced","canonical_anchor":"agent-api-error-recovery-partial-output-surfaced","heading":"Agent API Error Recovery: Partial Output Surfaced","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199\/e\/agent-api-error-recovery-partial-output-surfaced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.199","markdown":"### Agent API Error Recovery: Partial Output Surfaced\n\nWhen an agent (Task tool) terminates early due to an API error such as rate limiting, server overload, or server errors, Claude now recovers and presents the partial output the agent produced rather than discarding it entirely.\n\n**Details**\n\n- A new `AgentApiErrorTerminationError` class captures early terminations caused by `rate_limit`, `overloaded`, or `server_error` API error kinds\n- The partial agent history is surfaced with a clear notice: \"Everything below is PARTIAL output recovered from the agent before it was cut off. The agent did NOT finish its task \u2014 treat these results as incomplete.\"\n- This prevents complete loss of context when long-running agents hit transient API errors\n\n**Evidence**\n\n(search for `\"AgentApiErrorTerminationError\"`, `\"PARTIAL output recovered from the agent\"`)"}