codex - 💡(How to fix) Fix Windows browser-use external navigation fails when Codex helper bin path is missing [3 comments, 4 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#19562Fetched 2026-04-26 05:14:58
View on GitHub
Comments
3
Participants
4
Timeline
8
Reactions
1
Timeline (top)
labeled ×4commented ×3cross-referenced ×1

Error Message

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 external navigation should not fail with os error 3 when the app-server is already running and the IAB backend is active.

Root Cause

The issue is easy to miss because local browser navigation works. The failure only appears on external URLs because browser-use performs a remote site-status check through nodeRepl.fetch.

Fix Action

Fix / Workaround

Verification after workaround

Code Example

failed to start codex app-server: The system cannot find the path specified. (os error 3)

---

Node runtime too old for node_repl (resolved C:\Program Files\nodejs\node.exe): found v22.14.0, requires >= v22.22.0

---

failed to start codex app-server: The system cannot find the path specified. (os error 3)

---

%LOCALAPPDATA%\OpenAI\Codex\bin

---

%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\OpenAI\Codex\bin

---

codex.exe
node_repl.exe
node.exe
rg.exe
codex-command-runner.exe
codex-windows-sandbox-setup.exe
RAW_BUFFERClick to expand / collapse

What happened?

On Windows Codex Desktop, @browser-use could bootstrap the IAB backend and create/list tabs, but external navigation failed before loading the page.

The failure occurred on tab.goto("https://example.com/") during the authenticated site-status check:

failed to start codex app-server: The system cannot find the path specified. (os error 3)

Local navigation to http://127.0.0.1:<port>/ worked, so the browser backend itself was alive. External navigation was blocked by the host/app-server helper path used by nodeRepl.fetch.

Environment

  • OS: Windows
  • Codex Desktop package path: OpenAI.Codex_26.422.3464.0_x64__2p2nqsd0c76g0
  • Codex app-server: 0.125.0-alpha.3
  • browser-use: 0.1.0-alpha1
  • System Node after update: v24.15.0
  • node_repl.exe: app-packaged binary

Investigation

There were two separate problems.

  1. Initially, node_repl resolved old system Node:
Node runtime too old for node_repl (resolved C:\Program Files\nodejs\node.exe): found v22.14.0, requires >= v22.22.0

Updating system Node to v24.15.0 fixed node_repl startup.

  1. After Node was fixed, external navigation still failed with:
failed to start codex app-server: The system cannot find the path specified. (os error 3)

The desktop process had this path on PATH:

%LOCALAPPDATA%\OpenAI\Codex\bin

But that directory did not exist.

The actual helper binaries existed under the packaged app cache:

%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\OpenAI\Codex\bin

That directory contained:

codex.exe
node_repl.exe
node.exe
rg.exe
codex-command-runner.exe
codex-windows-sandbox-setup.exe

After mirroring those helper binaries into the expected %LOCALAPPDATA%\OpenAI\Codex\bin path, browser-use external navigation worked.

Verification after workaround

@browser-use successfully:

  1. Bootstrapped with setupAtlasRuntime({ backend: "iab" })
  2. Created/listed an IAB tab
  3. Navigated to https://example.com/
  4. Read the DOM/title
  5. Clicked the single anchor on the page
  6. Navigated to https://www.iana.org/help/example-domains

Expected behavior

Codex Desktop should either:

  • create/populate %LOCALAPPDATA%\OpenAI\Codex\bin, if that path is expected to be on PATH, or
  • put the actual packaged helper bin path on PATH, or
  • have node_repl/nodeRepl.fetch resolve the helper from the packaged app location directly.

browser-use external navigation should not fail with os error 3 when the app-server is already running and the IAB backend is active.

Notes

The issue is easy to miss because local browser navigation works. The failure only appears on external URLs because browser-use performs a remote site-status check through nodeRepl.fetch.

extent analysis

TL;DR

Mirroring the helper binaries into the expected %LOCALAPPDATA%\OpenAI\Codex\bin path or updating the PATH environment variable to include the actual packaged app cache location can resolve the external navigation failure.

Guidance

  • Verify that the %LOCALAPPDATA%\OpenAI\Codex\bin directory exists and contains the necessary helper binaries (e.g., codex.exe, node_repl.exe).
  • Check the PATH environment variable to ensure it includes the correct location of the helper binaries, either the expected %LOCALAPPDATA%\OpenAI\Codex\bin or the actual packaged app cache location.
  • Consider updating the Codex Desktop configuration to automatically create/populate the expected binary directory or update the PATH variable accordingly.
  • Test external navigation with browser-use after applying the workaround to ensure it resolves the os error 3 issue.

Example

No code snippet is provided as the issue is related to environment configuration and binary paths.

Notes

The issue may be specific to the Windows environment and the Codex Desktop package version OpenAI.Codex_26.422.3464.0_x64__2p2nqsd0c76g0. The workaround may need to be adapted for different versions or environments.

Recommendation

Apply the workaround by mirroring the helper binaries into the expected %LOCALAPPDATA%\OpenAI\Codex\bin path or updating the PATH environment variable, as this resolves the external navigation failure and allows browser-use to function correctly.

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…

FAQ

Expected behavior

Codex Desktop should either:

  • create/populate %LOCALAPPDATA%\OpenAI\Codex\bin, if that path is expected to be on PATH, or
  • put the actual packaged helper bin path on PATH, or
  • have node_repl/nodeRepl.fetch resolve the helper from the packaged app location directly.

browser-use external navigation should not fail with os error 3 when the app-server is already running and the IAB backend is active.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Windows browser-use external navigation fails when Codex helper bin path is missing [3 comments, 4 participants]