codex - 💡(How to fix) Fix Browser Use cannot navigate external sites because nodeRepl.fetch fails to start/find Codex app-server on Windows [2 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#21371Fetched 2026-05-07 03:41:04
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
Timeline (top)
labeled ×5commented ×2closed ×1

Error Message

Observed error: failed to start codex app-server: The system cannot find the path specified. (os error 3) failed to start codex app-server: The system cannot find the path specified. (os error 3) Browser Use should open https://www.google.com in the in-app browser, or return a clear external-site/network/auth error if the safety check fails. A later Codex extension/runtime error surfaced from codex_analytics::client, where the client appeared to receive a Cloudflare challenge HTML page instead of the expected API response. Raw Cloudflare challenge tokens are omitted. A later Codex extension/runtime error surfaced from codex_analytics::client, where the client appeared to receive a Cloudflare challenge HTML page instead of the expected API response. I am omitting the raw challenge tokens.

Code Example

failed to start codex app-server: The system cannot find the path specified. (os error 3)
The failure happens when Browser Use performs the external-site safety/status check through nodeRepl.fetch.

Basic IAB commands work:

setupAtlasRuntime({ globals: globalThis, backend: "iab" }) succeeds.
agent.browser.nameSession(...) succeeds.
agent.browser.tabs.list() succeeds.
agent.browser.tabs.selected() succeeds.
But this fails:

await tab.goto("https://www.google.com");
The underlying fetch also fails directly:

await nodeRepl.fetch("https://chatgpt.com/backend-api/aura/site_status?site_url=https%3A%2F%2Fwww.google.com%2F&url_request_source=codex_browser_use", { method: "GET" });
I also observed that nodeRepl.homeDir was null, and process.env appeared empty inside the Node REPL kernel.

Codex logs showed the app-server existed and reported version 0.128.0-alpha.1.

### What steps can reproduce the bug?

1. Open Codex Desktop on Windows with the in-app browser open.
2. Use the Browser Use plugin.
3. Run:

---

Current reported app-server version: currentVersion=0.128.0-alpha.1
Logs also showed runtime paths were selected:

codexCliPath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\codex.exe
nodePath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\node.exe
nodeReplPath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\node_repl.exe
nodeVersionValue=v24.14.0
platform=win32
A later Codex extension/runtime error surfaced from codex_analytics::client, where the client appeared to receive a Cloudflare challenge HTML page instead of the expected API response. Raw Cloudflare challenge tokens are omitted.

### Additional information

Restarting Codex Desktop did not fix the issue.

Resetting the Node REPL state did not fix it.

The main app-server process appeared to exist. Logs included:
RAW_BUFFERClick to expand / collapse

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

OpenAI.Codex_26.429.8261.0_x64

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Browser Use can connect to the in-app browser backend and basic tab commands work, but navigating to external sites fails before navigation.

Observed error:

failed to start codex app-server: The system cannot find the path specified. (os error 3)
The failure happens when Browser Use performs the external-site safety/status check through nodeRepl.fetch.

Basic IAB commands work:

setupAtlasRuntime({ globals: globalThis, backend: "iab" }) succeeds.
agent.browser.nameSession(...) succeeds.
agent.browser.tabs.list() succeeds.
agent.browser.tabs.selected() succeeds.
But this fails:

await tab.goto("https://www.google.com");
The underlying fetch also fails directly:

await nodeRepl.fetch("https://chatgpt.com/backend-api/aura/site_status?site_url=https%3A%2F%2Fwww.google.com%2F&url_request_source=codex_browser_use", { method: "GET" });
I also observed that nodeRepl.homeDir was null, and process.env appeared empty inside the Node REPL kernel.

Codex logs showed the app-server existed and reported version 0.128.0-alpha.1.

### What steps can reproduce the bug?

1. Open Codex Desktop on Windows with the in-app browser open.
2. Use the Browser Use plugin.
3. Run:

```js
const { setupAtlasRuntime } = await import("C:/Users/<user>/.codex/plugins/cache/openai-bundled/browser-use/0.1.0-alpha1/scripts/browser-client.mjs");
await setupAtlasRuntime({ globals: globalThis, backend: "iab" });
await agent.browser.nameSession("Google test");
Confirm basic tab commands work:
await agent.browser.tabs.list();
globalThis.tab = await agent.browser.tabs.selected();
Try to navigate to an external site:
await tab.goto("https://www.google.com");
It fails with:
failed to start codex app-server: The system cannot find the path specified. (os error 3)

### What is the expected behavior?

Browser Use should open `https://www.google.com` in the in-app browser, or return a clear external-site/network/auth error if the safety check fails.

Restarting Codex Desktop did not fix the issue.

Resetting Node REPL state did not fix it.

The main app-server process appeared to exist. Logs included:

```text
Current reported app-server version: currentVersion=0.128.0-alpha.1
Logs also showed runtime paths were selected:

codexCliPath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\codex.exe
nodePath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\node.exe
nodeReplPath=C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\node_repl.exe
nodeVersionValue=v24.14.0
platform=win32
A later Codex extension/runtime error surfaced from codex_analytics::client, where the client appeared to receive a Cloudflare challenge HTML page instead of the expected API response. Raw Cloudflare challenge tokens are omitted.

### Additional information

Restarting Codex Desktop did not fix the issue.

Resetting the Node REPL state did not fix it.

The main app-server process appeared to exist. Logs included:

```text
Current reported app-server version: currentVersion=0.128.0-alpha.1

Session/thread id from this run:
`019dfdeb-a356-7341-8e86-7137a288d467`

Logs also showed runtime paths were selected:


codexCliPath=C:\Users\HP\AppData\Local\OpenAI\Codex\bin\codex.exe
nodePath=C:\Users\HP\AppData\Local\OpenAI\Codex\bin\node.exe
nodeReplPath=C:\Users\HP\AppData\Local\OpenAI\Codex\bin\node_repl.exe
nodeVersionValue=v24.14.0
platform=win32
A later Codex extension/runtime error surfaced from codex_analytics::client, where the client appeared to receive a Cloudflare challenge HTML page instead of the expected API response. I am omitting the raw challenge tokens.

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