Codex app in-app browser automation fails with "failed to start codex app-server: The system cannot find the path specified. (os error 3)" on Windows
Resolved 💬 2 comments Opened Apr 30, 2026 by 7hcy9xqq7q-dotcom Closed Apr 30, 2026
I’m using Codex Desktop on Windows and browser automation is failing in the in-app browser.
What works:
- The Codex in-app browser opens correctly
- I can manually load pages in the in-app browser
- Example page:
https://casinobonusstreak.com/wp-admin/admin.php?page=fluentcrm-admin#/
- Node was updated and the earlier Node version issue appears resolved
What fails:
- As soon as Codex tries to inspect or control the live in-app browser tab, it errors with:
failed to start codex app-server: The system cannot find the path specified. (os error 3)
<img width="1898" height="1234" alt="Image" src="https://github.com/user-attachments/assets/ccada8be-5b8c-4451-8e13-c70f4862339b" />
Important details:
- This is happening inside the Codex in-app browser, not Firefox or another external browser
- The page is already open and visible in the Codex browser pane
- The failure happens when automation attempts to attach to or control the tab
Expected behavior:
- Codex should be able to inspect and control an already open in-app browser tab
Actual behavior:
- Codex throws the app-server path error and cannot automate the page
Steps to reproduce:
- Open Codex Desktop on Windows
- Open the in-app browser
- Navigate to a live page, for example:
https://casinobonusstreak.com/wp-admin/admin.php?page=fluentcrm-admin#/
- Ask Codex to inspect or control the current in-app browser tab
- Codex fails with:
failed to start codex app-server: The system cannot find the path specified. (os error 3)
Environment:
- Windows
- Codex Desktop
- In-app browser open on a logged-in WordPress / FluentCRM page
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗