{"version":"2.1.319","anchor":"chrome-tool-calls-that-lose-their-connection-now-return-an-e","canonical_anchor":"chrome-tool-calls-that-lose-their-connection-now-return-an-e","heading":"Browser actions that lose the Chrome connection now warn they may have happened","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-tool-calls-that-lose-their-connection-now-return-an-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Browser actions that lose the Chrome connection now warn they may have happened\n\nIf the Chrome connection drops after a browser action is sent, the model is told it may have happened and to check before repeating it\n\n**What**\n\nClaude Code can control a Chrome browser through browser tools. If the connection to Chrome drops after a browser action has been sent but before its result comes back, the model now receives a plain message saying the action may or may not have happened. The message tells it to:\n\n- simply call again if the action only reads from the page, and\n\n- otherwise check the page first, with `get_page_text` or a screenshot, before trying again.\n\nClaude Code also records the tool, the kind of connection and the cause of the drop.\n\n**Why**\n\nThis stops the model from blindly repeating an action, such as submitting a form or making a purchase, that may already have gone through.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}