codex - 💡(How to fix) Fix Windows Codex Desktop Browser Use fails to start app-server despite working npm CLI [4 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#20048Fetched 2026-04-29 06:23:29
View on GitHub
Comments
4
Participants
4
Timeline
9
Reactions
0
Timeline (top)
commented ×4labeled ×4cross-referenced ×1

Error Message

failed to start codex app-server: The system cannot find the path specified. (os error 3) A simple test like navigating to https://example.com fails with the same app-server error. failed to start codex app-server: The system cannot find the path specified. (os error 3) 5. This works, but Browser Use in Codex Desktop still fails with the same app-server error. For example, navigating to https://example.com through Browser Use should load the page and allow DOM/screenshot inspection instead of failing with an app-server path error.

Root Cause

So the standalone CLI appears healthy, but Codex Desktop Browser Use still fails, likely because it is trying to start the packaged WindowsApps codex.exe or otherwise not resolving the working codex.cmd from PATH.

RAW_BUFFERClick to expand / collapse

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

26.422.8496.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 10 Home, 64-bit, build 26100

What issue are you seeing?

Codex Desktop Browser Use does not work on Windows.

When I use the Browser Use plugin, it only sees an about:blank tab and cannot navigate or inspect the in-app browser. Attempting to navigate with Browser Use fails with:

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

Inside Codex, Browser Use returns:

agent.browser.tabs.list() => about:blank agent.browser.user.openTabs() => []

A simple test like navigating to https://example.com fails with the same app-server error.

I also tested the packaged Codex executable directly in PowerShell:

& "C:\Program Files\WindowsApps\OpenAI.Codex_26.422.8496.0_x64__2p2nqsd0c76g0\app\resources\codex.exe" --help

That fails with:

Access is denied

I installed the standalone npm CLI:

npm.cmd install -g @openai/codex

Then:

codex.cmd app-server --help

works correctly and prints the app-server help text.

So the standalone CLI appears healthy, but Codex Desktop Browser Use still fails, likely because it is trying to start the packaged WindowsApps codex.exe or otherwise not resolving the working codex.cmd from PATH.

I already tried:

  • Restarting Windows
  • Terminating Codex
  • Repairing Codex from Windows Apps settings
  • Resetting Codex
  • Uninstalling/reinstalling Codex Desktop
  • Fully quitting/reopening Codex Desktop
  • Installing the npm CLI

The issue still persists.

What steps can reproduce the bug?

  1. Install and open Codex Desktop on Windows.
  2. Open a Codex thread with the Browser Use plugin enabled.
  3. Ask Codex to use Browser Use or run a basic Browser Use navigation test.
  4. Browser Use initializes but only sees an about:blank tab.
  5. Attempt to navigate the Browser Use tab to a simple site such as https://example.com.
  6. The navigation fails with:

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

Additional reproduction/check:

  1. In PowerShell, run the packaged Codex executable directly:

& "C:\Program Files\WindowsApps\OpenAI.Codex_26.422.8496.0_x64__2p2nqsd0c76g0\app\resources\codex.exe" --help

  1. It fails with:

Access is denied

  1. Install standalone CLI:

npm.cmd install -g @openai/codex

  1. Run:

codex.cmd app-server --help

  1. This works, but Browser Use in Codex Desktop still fails with the same app-server error.

What is the expected behavior?

Browser Use should start or connect to a working Codex app-server, attach to the in-app browser tab, and allow normal browser automation actions such as navigation, screenshots, DOM snapshots, clicks, and form interactions.

For example, navigating to https://example.com through Browser Use should load the page and allow DOM/screenshot inspection instead of failing with an app-server path error.

Additional information

Additional context: I am logged into GitHub with a different account than my ChatGPT/Codex account. I do not know if this is related, but I wanted to mention it. The Browser Use failure appears to happen before any GitHub-specific action, during Codex app-server startup/navigation. [email protected] is my account for codex

extent analysis

TL;DR

The issue is likely due to Codex Desktop Browser Use trying to start the packaged WindowsApps codex.exe, which is not working, instead of using the standalone CLI version that is installed and functional.

Guidance

  • The error message "failed to start codex app-server: The system cannot find the path specified. (os error 3)" suggests that Codex Desktop is trying to use the wrong executable.
  • The fact that running codex.cmd app-server --help works correctly in PowerShell, but the packaged Codex executable does not, implies a path or executable resolution issue.
  • To mitigate this, try modifying the Codex Desktop configuration to use the standalone CLI version of codex.cmd instead of the packaged executable.
  • Verify that the PATH environment variable includes the directory where codex.cmd is installed, to ensure that Codex Desktop can find and use the correct executable.

Example

No code snippet is provided as the issue seems to be related to executable resolution and configuration rather than code.

Notes

The issue might be specific to the Windows 10 environment and the way Codex Desktop interacts with the packaged versus standalone CLI versions of the codex executable. The fact that the user is logged into GitHub with a different account than their ChatGPT/Codex account is unlikely to be related to the issue.

Recommendation

Apply a workaround by configuring Codex Desktop to use the standalone CLI version of codex.cmd, as this version is known to be functional and can correctly start the app-server.

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