You'll notice
Browser tab-lookup timeout error now also suggests the browser's machine may be offline or asleep
What
When 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.
Why
This 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.