{"version":"2.1.299","anchor":"chrome-tool-connection-lost-classification-by-error-name","canonical_anchor":"chrome-tool-connection-lost-classification-by-error-name","heading":"Lost Chrome connections are now reported correctly","tier":"internal","area":"Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/chrome-tool-connection-lost-classification-by-error-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Lost Chrome connections are now reported correctly\n\nClaude Code now correctly labels Chrome browser tool failures caused by a dropped connection as a lost connection\n\n**What**\n\nWhen a tool call to the Chrome browser extension fails, Claude Code sorts the failure into a category for its error reports. Failures caused by a dropped socket connection or a lost tool call are now labelled \"connection lost\" by checking the error's name. The earlier check looked at the wrong value, so these failures were not labelled that way.\n\n**Why**\n\nError reports and diagnostics for the browser extension now say more accurately when a failure was caused by a lost connection.\n\n- Area: Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}