{"version":"2.1.268","anchor":"hidden-tabs-context-mcp-lookup-failure-message-now-covers-of","canonical_anchor":"hidden-tabs-context-mcp-lookup-failure-message-now-covers-of","heading":"Hidden tabs_context_mcp lookup failure message now covers offline\/asleep browser host","tier":"notice","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/hidden-tabs-context-mcp-lookup-failure-message-now-covers-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Hidden tabs_context_mcp lookup failure message now covers offline\/asleep browser host\n\nBrowser tab-lookup timeout error now also suggests the browser's machine may be offline or asleep\n\n**What**\n\nWhen a hidden lookup used internally by `navigate` (`tabs_context_mcp`) times out waiting for a response, the resulting error message now also mentions that the machine running the Chrome extension's browser could be offline or asleep, in addition to the existing possibility that the extension itself was just slow to start.\n\n**Why**\n\nThis gives a more accurate and actionable explanation when browser-based tools fail to respond, since a sleeping or disconnected machine is a distinct problem from a slow-starting extension and points toward a different fix.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}