Browserbase MCP connector disconnects mid-session, dropping start/navigate/extract without warning

During an active Cowork session using the Browserbase custom MCP connector (mcp__Browserbase__*), the connector disconnected mid-task. mcp__Browserbase__start, navigate, and extract had all been working normally seconds earlier (used repeatedly across ~10 tool calls in the same conversation), then on the next call they vanished from the tool list entirely — a system reminder reported "The following deferred tools are no longer available (their MCP server disconnected)" for all Browserbase tools.

A subsequent RefreshMcpTools call for the Browserbase server returned {"status":"error","error":"Not connected"}, confirming the server-side connection had dropped rather than a client-side tool-listing glitch.

This happened with an active Browserbase session still open (a live browser waiting on a login page), so the disconnect stranded that session mid-task — it had to be handed to the user as a raw debug URL instead of being driven and verified programmatically.

No user action (like a reconnect prompt) preceded the drop. No error was surfaced until the next tool call attempt.

Impact: any in-progress Browserbase automation can be silently killed mid-session with no warning, leaving open (billed) sessions that can't be verified or closed by the agent until the connector reconnects on its own.