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
- Install Codex Chrome Extension
- Enable Chrome control in Codex Desktop
- Confirm Chrome appears as “Connected”
- Start a new task
- Ask Codex:
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
- Install Codex Chrome Extension
- Enable Chrome control in Codex Desktop
- Confirm Chrome appears as “Connected”
- Start a new task
- Ask Codex:
or:
使用浏览器打开 GitHub 并 fork 一个仓库
What is the expected behavior?
No response
Additional information
No response
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
@chromeautomation tool is unavailable on WindowsEnvironment
Problem
Codex Desktop settings show Chrome as successfully connected:
However, when using
@chromein a task, Codex always responds with:or cannot perform browser automation actions.
Reproduction
or:
Actual Result
Codex says:
@chromeautomation toolEven though the Chrome integration UI still shows “Connected”.
Expected Result
If Chrome shows as connected in settings,
@chromeautomation should be available to the agent runtime.Additional Notes
This looks like:
UI layer appears connected, but automation backend is unavailable.
Possibly related to:
What steps can reproduce the bug?
Reproduction
or:
What is the expected behavior?
No response
Additional information
No response