豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

docs: fix Codex MCP add instructions#968

Closed
liuxiaopai-ai wants to merge 6 commits intoChromeDevTools:mainfrom
liuxiaopai-ai:docs/fix-codex-mcp-add
Closed

docs: fix Codex MCP add instructions#968
liuxiaopai-ai wants to merge 6 commits intoChromeDevTools:mainfrom
liuxiaopai-ai:docs/fix-codex-mcp-add

Conversation

@liuxiaopai-ai
Copy link
Copy Markdown

Fixes #967.

  • Update README Codex install command to use npx -y (matches the recommended config and avoids interactive prompts).
  • Add a quick verification step (codex mcp list).
  • Document the common error: unexpected argument 'add' found case (older Codex CLIs) and provide a .codex/config.toml fallback snippet.
  • Add the same troubleshooting note to docs/troubleshooting.md.

@google-cla
Copy link
Copy Markdown

google-cla bot commented Feb 16, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@liuxiaopai-ai
Copy link
Copy Markdown
Author

Rebased on latest main and resolved merge conflicts in docs/troubleshooting.md.

Also ran:

  • npm ci
  • npm run check-format

(Added missing license header + formatting for the remote debugging example so eslint/prettier passes.)

Note: cla/google will stay red until the PR author signs the Google CLA.

@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented Feb 18, 2026

Could you please sign the CLA?

Comment thread docs/troubleshooting.md

## Specific problems

### Codex: `error: unexpected argument 'add' found`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if the latest codex version supports add, then we probably should not need to document it as users will upgrade soon?

Comment thread docs/troubleshooting.md

Point the MCP connection inside the VM to `http://127.0.0.1:9222`. This allows DevTools to reach the host browser without triggering the Host validation error.

### Connecting to a running Chrome instance (remote debugging, 9222)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this does not seem to be related to codex. Please remove this section.

@@ -0,0 +1,55 @@
/**
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this example (not related to codex).

Comment thread README.md

Verification: run `codex mcp list` and confirm `chrome-devtools` is listed.

If you see `error: unexpected argument 'add' found`, your Codex CLI is too old to support `codex mcp add`.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we be more specific in which codex version does add work?

@OrKoN OrKoN mentioned this pull request Feb 18, 2026
github-merge-queue bot pushed a commit that referenced this pull request Feb 18, 2026
@OrKoN OrKoN closed this in #987 Feb 18, 2026
madhaviai pushed a commit to madhaviai/chrome-devtools-mcp that referenced this pull request Feb 18, 2026
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: instructions to use with codex are not working

3 participants