{"version":"2.1.179","anchor":"better-messages-when-api-connection-drops","canonical_anchor":"better-messages-when-api-connection-drops","heading":"Better Messages When API Connection Drops","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.179\/e\/better-messages-when-api-connection-drops","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.179","markdown":"### Better Messages When API Connection Drops\n\nThree new user-facing messages now appear when a streaming connection is lost:\n\n- Mid-response (after some content was already delivered): `Connection closed mid-response. The response above may be incomplete.`\n- During thinking (before any content): `Connection closed while thinking, before producing a response. Try again.`\n- Network-level errors (ECONNRESET, EPIPE, etc.): `Connection to the API was lost (<error_code>). This is usually temporary \u2014 try again.`\n\nPreviously these all surfaced as generic error messages.\n\n**Evidence**\n\nStream-drop messages (search for `\"Connection closed mid-response\"` and `\"Connection closed while thinking\"`) and network-error handler (search for `\"Connection to the API was lost (\"`)"}