Could you add to Readme a description how to run Chrome MCP with Codex under WSL?

[it-sha]

Description of the bug

The best solution I have found #131 (comment)

It works with Claude Code but not with Codex

Reproduction

1. Set codex config.toml

[mcp_servers.chrome-devtools]
command = "npx"
args = [
    "chrome-devtools-mcp@latest",
    "--executablePath",
    "/home/max/chrome/chrome/linux-141.0.7390.122/chrome-linux64/chrome",
    "--no-sandbox",
    "--disable-setuid-sandbox",
    "--categoryPerformance=false",
    "--categoryEmulation=false",
    "--categoryNetwork=false",
]

2. Run mcp
   See error

Called chrome-devtools.new_page({"timeout":120000,"url":"https://ya.ru"})
  └ Missing X server to start the headful browser. Either set headless to true or use xvfb-run to run your Puppeteer script.

Expectation

No response

MCP configuration

[mcp_servers.chrome-devtools]
command = "npx"
args = [
"chrome-devtools-mcp@latest",
"--executablePath",
"/home/max/chrome/chrome/linux-141.0.7390.122/chrome-linux64/chrome",
"--no-sandbox",
"--disable-setuid-sandbox",
"--categoryPerformance=false",
"--categoryEmulation=false",
"--categoryNetwork=false",
]

Chrome DevTools MCP version

0.9.0

Chrome version

chrome/linux-141.0.7390.122/chrome-linux64

Coding agent version

OpenAI Codex (v0.53.0)

Model version

No response

Chat log

No response

Node version

No response

Operating system

None

Extra checklist

• I want to provide a PR to fix this bug

[OrKoN]

Thanks for reporting, the args

    "--no-sandbox",
    "--disable-setuid-sandbox",

have no effect here because the MCP server does not forward all args to Chrome. Have you tried adding the --headless flag instead because it does not appear that the environment has an X server? There are many ways to run Chrome with WSL depending on specific WSL and Windows versions. In general, the easiest way seems to be point the MCP server to the installation on the Windows side by passing --executable-path=/mnt/c/Program\\ Files/Google/Chrome/Application/chrome.exe (or the path where you have Chrome installed). Does that work for you?

[it-sha]

Have you tried adding the --headless flag instead because it does not appear that the environment has an X server?

Yes. Part of the functionality is not working in this case. E.g. screenshots

In general, the easiest way seems to be point the MCP server to the installation on the Windows side by passing --executable-path=/mnt/c/Program\ Files/Google/Chrome/Application/chrome.exe (or the path where you have Chrome installed). Does that work for you?

Thank you for the advice. I will check

[tovupixel]

Got it working in codex under WSL:

First run:
npx -y @puppeteer/browsers install chrome@stable --path ~/chrome

then once chrome is installed do:
sudo env "PATH=$PATH" npx -y @puppeteer/browsers install chrome@stable --path ~/chrome --install-deps

Then adjust: "~/.codex/config.toml"

Add/modify this bit:

[mcp_servers.chrome-devtools]
command = "npx"
args = [
  "-y",
  "chrome-devtools-mcp@latest",
  "--executablePath",
  "/home/{your_username}/chrome/chrome/{chrome_version}/chrome-linux64/chrome",
  "--headless=true",
  "--isolated=true",
  "--logFile=/tmp/chrome-devtools-mcp.log"
]

env = { DEBUG = "*" }
startup_timeout_ms = 30000

Now you should be able to do:

/home/{username}/chrome/chrome/{chrome_version}/chrome-linux64/chrome --headless=new --no-sandbox --disable-setuid-sandbox --remote-debugging-port=9222 https://example.com

and see it working.

[rootd4ddy]

I had the same issue, an X server was in fact available. I fixed it like so:

{"mcpServers":{"chrome-devtools":{"command":"bash","args":["-lc","DISPLAY=:1 XAUTHORITY=$HOME/.Xauthority npx -y chrome-devtools-mcp@latest --isolated"],"alwaysAllow":["new_page"]}}}

[Elehiggle]

I had the same issue, an X server was in fact available. I fixed it like so:

{"mcpServers":{"chrome-devtools":{"command":"bash","args":["-lc","DISPLAY=:1 XAUTHORITY=$HOME/.Xauthority npx -y chrome-devtools-mcp@latest --isolated"],"alwaysAllow":["new_page"]}}}

Thanks, works wonderfully without any real requirements:

[mcp_servers.chrome-devtools]
command = "bash"
args = [
  "-lc",
  "DISPLAY=${DISPLAY:-:0} XAUTHORITY=${XAUTHORITY:-$HOME/.Xauthority} npx -y chrome-devtools-mcp@latest --executablePath /home/user/chrome/chrome/linux-143.0.7499.42/chrome-linux64/chrome --headless=false --isolated=false --logFile=/tmp/chrome-devtools-mcp.log --viewport 390x844"
]
env = { DEBUG = "*" }
startup_timeout_ms = 30000

[dbalabka]

So, I ended up with a shell script that checks and applies all required Windows settings and then starts already installed Windows Chrome with the proper configuration:
https://github.com/dbalabka/chrome-wsl/

You can simply start Chrome (the initial run may require applying some Windows tweaks):

npx @dbalabka/chrome-wsl

To stop Chrome:

npx @dbalabka/chrome-wsl --stop

To completely clean up the applied Windows settings:

npx @dbalabka/chrome-wsl --uninstall

If you want to run the agent inside a Docker container, you can ask the script to apply the required adjustments inside the container as well:

npx @dbalabka/chrome-wsl --container=<name>

To setup to DevTools MCP you need the following settings:

[mcp_servers.chome-devtools]
command = "npx"
args = ["-y", "chrome-devtools-mcp@latest", "--browser-url=http://127.0.0.1:9222"]
startup_timeout_sec = 20.0

[austinedfizer-lab]

I have found a problem with Gemini And Google voice that we would like guidance on how to go about this issue And, there are some other issues to discuss as well.. So, can a developer get with us and we can discuss some things?

…

On Mon, Jan 5, 2026, 1:19 PM Dmitry Balabka ***@***.***> wrote: *dbalabka* left a comment (ChromeDevTools/chrome-devtools-mcp#509) <#509 (comment)> So, I ended up with a shell script that checks and applies all required Windows settings and then starts already installed Windows Chrome with the proper configuration: https://github.com/dbalabka/chrome-wsl/ You can simply start Chrome (the initial run may require applying some Windows tweaks): npx @dbalabka/chrome-wsl To stop Chrome: npx @dbalabka/chrome-wsl --stop To completely clean up the applied Windows settings: npx @dbalabka/chrome-wsl --uninstall If you want to run the agent inside a Docker container, you can ask the script to apply the required adjustments inside the container as well: npx @dbalabka/chrome-wsl --container=<name> To setup to DevTools MCP you need the following settings: [mcp_servers.chome-devtools] command = "npx" args = ["-y", ***@***.***", "--browser-url=http://127.0.0.1:9222"] startup_timeout_sec = 20.0 — Reply to this email directly, view it on GitHub <#509 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYGGH45CSX23K4T5WHJ7LT34FKTLLAVCNFSM6AAAAACK42YKVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJRGU4DOMRRG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tfeutren]

Got it working in codex under WSL:

First run: npx -y @puppeteer/browsers install chrome@stable --path ~/chrome

then once chrome is installed do: sudo env "PATH=$PATH" npx -y @puppeteer/browsers install chrome@stable --path ~/chrome --install-deps

Then adjust: "~/.codex/config.toml"

Add/modify this bit:

[mcp_servers.chrome-devtools]
command = "npx"
args = [
  "-y",
  "chrome-devtools-mcp@latest",
  "--executablePath",
  "/home/{your_username}/chrome/chrome/{chrome_version}/chrome-linux64/chrome",
  "--headless=true",
  "--isolated=true",
  "--logFile=/tmp/chrome-devtools-mcp.log"
]

env = { DEBUG = "*" }
startup_timeout_ms = 30000

Now you should be able to do:

/home/{username}/chrome/chrome/{chrome_version}/chrome-linux64/chrome --headless=new --no-sandbox --disable-setuid-sandbox --remote-debugging-port=9222 https://example.com

and see it working.

Still doesn't work with this I now have the following error :
Protocol error (Target.setDiscoverTargets): Target closed Cause:

[gmanio]

same

Protocol error (Target.setDiscoverTargets): Target closed\nCause:

this related be pipe options.

how to disable { pipe: false } options?

[OrKoN]

Added WSL instructions to https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md#wsl