Chrome control bridge is not injected into new Codex App tasks on Windows
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.4045.0
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Expected behavior
After selecting @chrome in a newly created Codex App task, the task should receive the Chrome control bridge and be able to navigate the user's existing Chrome profile.
Actual behavior
The Chrome plugin, Chrome extension, and Native Host are installed and enabled, but new Codex App tasks do not receive a usable Chrome control tool.
A task asked to open https://www.douyin.com responds that no Chrome/browser control bridge is available. The required callable bridge (mcp__node_repl__js) is absent from the task, so Chrome control cannot be initialized.
This prevents any Chrome interaction. No alternative browser or web search was used.
Impact
Chrome automation is unavailable even after fully restarting Codex Desktop and Chrome and creating a new task.
What steps can reproduce the bug?
Feedback ID: 019f747a-fc01-7b33-a650-ea5a13d2c764
What is the expected behavior?
- On Windows, fully quit Codex Desktop and Google Chrome.
- Start Chrome, then start Codex Desktop.
- Create a completely new task; do not continue or fork an older task.
- Select
@chrome. - Send this prompt:
打开 https://www.douyin.com
- Observe that the task reports no usable Chrome control bridge instead of opening the page.
Local verification already performed
- Codex App version: 26.715.4045.0
- Windows: Microsoft Windows NT 10.0.26200.0 x64
- Chrome extension is installed and enabled.
- Chrome Native Host manifest validation passes.
- Chrome and Browser plugins are enabled.
- The failure is that the new task does not receive the callable Chrome control bridge.
Feedback ID: 019f747a-fc01-7b33-a650-ea5a13d2c764
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗