Session closes when native Serial/Bluetooth picker opens #917
Description
Description of the bug
When triggering native device pickers from an MCP-controlled Chrome session, the session closes immediately.
This happens for both:
navigator.serial.requestPort()(Web Serial)navigator.bluetooth.requestDevice()(Web Bluetooth)
In my run, the tool fails with:
Protocol error (Accessibility.getFullAXTree): Session closed. Most likely the page has been closed.
The same flows work in regular (non-MCP) Chrome on the same machine.
Reproduction
- Start chrome-devtools-mcp and open a page with Web Serial or Web Bluetooth connect flow.
- Example:
https://client.meshtastic.org->New Connection->Bluetooth->New device. - As soon as the native picker should appear, MCP session detaches/closes and page context is lost (often reset to
about:blank).
Expectation
The browser/session should remain attached while the native picker opens or is canceled, so automation can continue after the picker closes.
MCP configuration
Using chrome-devtools-mcp through OpenCode's MCP integration (no special custom flags in this run).
Chrome DevTools MCP version
0.16.0
Chrome version
Google Chrome 144.0.7559.133
Coding agent version
OpenCode CLI
Model version
openai/gpt-5.3-codex
Chat log
N/A
Node version
v22.20.0
Operating system
macOS
Extra checklist
- I want to provide a PR to fix this bug