What version of the Codex App are you using?
26.915.31945, build 9922
What subscription do you have?
Personal workspace.
What platform is your computer?
macOS 26.6.2 (25G83)
What issue are you seeing?
Browser Use cannot discover or control any browser tabs in Codex Desktop. The failure affects both the official Chrome extension and the built-in browser.
Chrome is running, the extension is enabled, Chrome shows Manage in Settings > Computer Use, the correct Chrome profile is selected, and the target site is not blocked. Browser inventory remains empty and the request fails after approximately 30 seconds with:
nodeRepl.fetch request failed
The desktop app simultaneously logs:
No ChatGPT browser route is available for browser session 01a0bd41-0825-7203-b958-ddb89e031363
The visible built-in browser tab is registered under a client-new-thread placeholder while its owner route points to the actual Codex task ID. A newly created Codex task reproduces the same failure.
Native Computer Use is working: it successfully opened macOS Calculator, entered 7 + 5, and read the displayed result 12. This isolates the problem to the browser-session control path rather than general Computer Use permissions or routing.
What steps can reproduce the bug?
- Open Codex Desktop on macOS and start a local task.
- Enable the official Chrome integration in Settings > Computer Use, or open the built-in browser.
- Open a normal webpage in the browser.
- Ask Codex to read or list the current browser tabs.
- Wait approximately 30 seconds.
- Observe that browser inventory is empty and the request fails with
nodeRepl.fetch request failed.
- Check the desktop log and observe
No ChatGPT browser route is available for browser session ... during the same request.
The issue reproduces in an existing task and a newly created task, with Chrome and the built-in browser.
What is the expected behavior?
Codex Desktop should initialize a browser route for the current task, return the available browser and tab IDs, and allow the task to operate only its bound tab. Chrome and built-in browser tab discovery should not time out.
Additional information
- Feedback/session ID:
01a0bd41-0825-7203-b958-ddb89e031363
- Chrome: 153.0.8010.53
- Official ChatGPT Chrome extension: 1.26.901.11451
- Chrome plugin: 26.915.31945
- Official extension and Native Messaging checks pass.
- Reinstalling the official desktop app/plugin, restarting the extension host, restarting Chrome, restarting macOS, and testing a fresh Codex task did not resolve the issue.
- The issue reproduces on the original network and a phone hotspot.
- It also reproduces after switching to another proxy node. During the second-node test, connections to
chatgpt.com:443 and ws.chatgpt.com:443 were recorded without matching network, TLS, WebSocket, or timeout errors.
- Native Computer Use works with Calculator, confirming the problem is browser-specific.
- Attach
OpenAI支持-可直接粘贴35行-2026-09-22.txt and the diagnostic package to this report.
OpenAI支持-可直接粘贴35行-2026-09-22.txt
What version of the Codex App are you using?
26.915.31945, build 9922
What subscription do you have?
Personal workspace.
What platform is your computer?
macOS 26.6.2 (25G83)
What issue are you seeing?
Browser Use cannot discover or control any browser tabs in Codex Desktop. The failure affects both the official Chrome extension and the built-in browser.
Chrome is running, the extension is enabled, Chrome shows Manage in Settings > Computer Use, the correct Chrome profile is selected, and the target site is not blocked. Browser inventory remains empty and the request fails after approximately 30 seconds with:
The desktop app simultaneously logs:
The visible built-in browser tab is registered under a
client-new-threadplaceholder while its owner route points to the actual Codex task ID. A newly created Codex task reproduces the same failure.Native Computer Use is working: it successfully opened macOS Calculator, entered
7 + 5, and read the displayed result12. This isolates the problem to the browser-session control path rather than general Computer Use permissions or routing.What steps can reproduce the bug?
nodeRepl.fetch request failed.No ChatGPT browser route is available for browser session ...during the same request.The issue reproduces in an existing task and a newly created task, with Chrome and the built-in browser.
What is the expected behavior?
Codex Desktop should initialize a browser route for the current task, return the available browser and tab IDs, and allow the task to operate only its bound tab. Chrome and built-in browser tab discovery should not time out.
Additional information
01a0bd41-0825-7203-b958-ddb89e031363chatgpt.com:443andws.chatgpt.com:443were recorded without matching network, TLS, WebSocket, or timeout errors.OpenAI支持-可直接粘贴35行-2026-09-22.txtand the diagnostic package to this report.OpenAI支持-可直接粘贴35行-2026-09-22.txt