Windows Desktop: chrome-devtools list_pages times out with --autoConnect, while standalone MCP client succeeds

Environment

• Windows
• OpenCode Desktop: 1.18.29
• chrome-devtools-mcp: 1.8.0
• Chrome: 152
• Existing Chrome profile with multiple tabs and extensions
• Remote debugging enabled at chrome://inspect/#remote-debugging

Problem

After accepting Chrome's remote-debugging permission prompt,
chrome-devtools_list_pages fails inside OpenCode with:

MCP error -32001: Request timed out

Chrome shows its automation banner, but OpenCode cannot reliably
list or interact with my existing tabs. Some pages appear stuck
loading during the failure; an actual repeated reload has not
been confirmed.

Reproduction

1. Keep normal Chrome open with existing tabs.
2. Enable remote debugging and configure chrome-devtools-mcp
   with --autoConnect.
3. Start OpenCode Desktop.
4. Ask it to call list_pages.
5. Accept Chrome's connection permission if prompted.
6. The tool call times out.

Configuration

Initially:
{
"mcp": {
"chrome-devtools": {
"type": "local",
"command": [
"cmd", "/c", "npx", "-y",
"chrome-devtools-mcp@latest",
"--autoConnect",
"--no-usage-statistics",
"--no-performance-crux"
],
"timeout": 60000,
"enabled": true
}
}
}

Also reproduced after installing version 1.8.0 locally and
replacing cmd/npx with a direct node.exe invocation of
chrome-devtools-mcp/build/src/bin/chrome-devtools-mcp.js,
keeping the same flags and timeout.

Important comparison

A standalone Node diagnostic client launching the MCP server
over stdio successfully calls initialize and tools/call
(list_pages) against the same running Chrome profile.

Successful tests took approximately 6–19 seconds.

The standalone test also succeeded when advertising the MCP
roots capability and responding to roots/list.

OpenCode's integrated tool call still timed out after restarts.

Troubleshooting already attempted

• Restarted OpenCode.
• Disabled and re-enabled Chrome remote debugging.
• Stopped DevTools MCP processes and tested fresh connections.
• Set the per-server timeout to 60000.
• Removed the cmd/npx launch chain and used direct Node.
• Verified that standalone connections see the real profile,
  not a guest or separate automation profile.

None resolved the integrated OpenCode timeout.

Log observations

An earlier failing server log showed:

• list_pages request received
• Puppeteer connected
• list_pages context resolved
• Getting DevTools UI data
• No DevTools page detected
• A subsequent document.title evaluation without a matching
  response in the captured log

This does not establish the root cause.

Related issues

• https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/775
• https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/870
• https://github.com/anomalyco/opencode/issues/8701

Could this be an OpenCode Desktop MCP transport/lifecycle issue,
or an interaction with autoConnect and suspended tabs?
What targeted diagnostics would distinguish these possibilities?

Reproduction

No response

Expectation

No response

MCP configuration

No response

Chrome DevTools MCP version

1.8.0

Chrome version

No response

Coding agent version

No response

Model version

No response

Chat log

No response

Node version

No response

Operating system

Windows

Extra checklist

• I want to provide a PR to fix this bug

Start with chrome-devtools-mcp/build/src/bin/chrome-devtools-mcp.js and the list_pages path described in the logs. Compare the OpenCode stdio lifecycle with the standalone Node diagnostic client, including roots/list and autoConnect behavior. Done means identifying whether the timeout is caused by MCP transport/lifecycle handling or Chrome tab discovery, with a reproducible diagnostic distinction.