codex - 💡(How to fix) Fix Codex Desktop shows Chrome as connected, but @chrome automation tool is unavailable on Windows [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#22079Fetched 2026-05-11 03:19:26
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×4commented ×1mentioned ×1subscribed ×1

Code Example

@chrome open google.com

---

使用浏览器打开 GitHub 并 fork 一个仓库

---

@chrome open google.com

---

使用浏览器打开 GitHub 并 fork 一个仓库
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.506.31421

What subscription do you have?

plus

What platform is your computer?

No response

What issue are you seeing?

Codex Desktop shows Chrome as connected, but @chrome automation tool is unavailable on Windows

Environment

  • OS: Windows 11
  • Codex Desktop: latest version
  • Chrome Extension: installed and enabled
  • Chrome: latest stable

Problem

Codex Desktop settings show Chrome as successfully connected:

已连接到浏览器扩展程序,可进行更多控制

However, when using @chrome in a task, Codex always responds with:

我这边没有可用的 @chrome 自动化工具

or cannot perform browser automation actions.


Reproduction

  1. Install Codex Chrome Extension
  2. Enable Chrome control in Codex Desktop
  3. Confirm Chrome appears as “Connected”
  4. Start a new task
  5. Ask Codex:
@chrome open google.com

or:

使用浏览器打开 GitHub 并 fork 一个仓库

Actual Result

Codex says:

  • no available @chrome automation tool
  • browser automation unavailable
  • cannot click/confirm actions

Even though the Chrome integration UI still shows “Connected”.


Expected Result

If Chrome shows as connected in settings, @chrome automation should be available to the agent runtime.


Additional Notes

This looks like:

  • extension connection succeeds
  • but browser automation runtime / bridge is not actually registered

UI layer appears connected, but automation backend is unavailable.

Possibly related to:

  • Windows native host startup failure
  • browser bridge runtime crash
  • extension/Desktop version mismatch
  • multi-profile Chrome attach issue

What steps can reproduce the bug?

Reproduction

  1. Install Codex Chrome Extension
  2. Enable Chrome control in Codex Desktop
  3. Confirm Chrome appears as “Connected”
  4. Start a new task
  5. Ask Codex:
@chrome open google.com

or:

使用浏览器打开 GitHub 并 fork 一个仓库

What is the expected behavior?

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING