A proxy that holds Chrome's debug pipe so MCP tools stop stealing focus on macOS

ravann4 · reddit · 2026-10-02

The problem

On macOS, any tool connecting to Chrome over its debug WebSocket port activates the Chrome window — chrome-devtools-mcp and Playwright MCP in extension mode both trigger it, and no bringToFront: false setting helps.

The fix

The author found Chrome started with --remote-debugging-pipe doesn't activate — but the pipe can only be used by the process that spawned Chrome. So this proxy becomes the launcher: it starts Chrome with the pipe and exposes the exact same HTTP/WebSocket interface as --remote-debugging-port (//version, //list, a browser-level WebSocket). chrome-devtools-mcp connects via --browserUrl without knowing it isn't a real debug port, and multiple clients can share the single pipe (the proxy remaps request ids and routes responses back).

Other details

Forked from mimkorn/chrome-pipe-proxy; 500 lines of Node, MIT licensed.

Original post →

More from coding & agent

coding & agent channel →