openai / openai/codex

Unable to use browser plugin even after update and repair

Open
#39,543 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug computer-use sandbox windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.814.5517.0

What subscription do you have?

Pro

What platform is your computer?

Windows 11 x64 realse no. 25H2

What issue are you seeing?

Title: Codex Windows browser and computer-control helpers fail during sandbox startup

Product: Codex desktop app for Windows

Summary

Browser control and Windows Computer Use cannot start. Both fail before connecting to a browser, enumerating windows, selecting a tab, or making any network request.

Environment

  • Codex package version: 26.814.5517.0
  • Browser plugin version: 26.814.41957
  • Computer Use plugin version: 26.814.41957
  • Platform: Windows, x64
  • Windows release: 25H2
  • Windows build: 26200.9168
  • Computer-use runtime: 0.0.8/20260818003901-c66628846294-pr-1311460
  • Bundled Node version: 24.19.0

Exact error

node_repl kernel exited unexpectedly

node_repl diagnostics:
{"kernel_status":"exited(code=1)","kernel_stderr_tail":"windows sandbox failed: orchestrator_helper_incomplete: setup helper exited successfully before setup completed","reason":"stdout_eof","stream_error":null}

Steps to reproduce

  1. Open the Codex Windows desktop app.
  2. Start or continue a task requiring the in-app browser.
  3. Attempt to initialize browser control and connect to any URL.
  4. The helper process exits after approximately 3–6 seconds.
  5. Attempting Windows Computer Use produces the same sandbox-helper failure.

Expected result

The helper should initialize, connect to the browser or Windows desktop, and return available tabs or windows.

Actual result

The supporting runtime exits with code 1 before browser discovery or Windows enumeration begins. No tab, page, or application is reached.

Troubleshooting already completed

  • Updated Codex from 26.814.5167.0 to 26.814.5517.0.
  • Confirmed the updated executable is running.
  • Fully closed and reopened Codex.
  • Restarted Windows.
  • Used Windows Installed Apps → Codex → Advanced options → Repair.
  • Signed out of Codex and signed back in.
  • Retried with multiple fresh helper sessions.
  • Changed to a different network.
  • Retried browser control after every troubleshooting step.
  • Retried using Windows Computer Use as a fallback.

The result and exact error remained unchanged after every step.

Additional observations

  • The failure occurs during local Windows sandbox/helper startup.
  • It happens before any browser connection, URL navigation, authentication, or external network request.
  • Changing networks had no effect.
  • It affects both the Browser and Computer Use capabilities, suggesting a shared local runtime or sandbox-helper problem.
  • Normal Codex chat, repository inspection, and command execution continue to work.
  • The issue blocks workflows requiring access to authenticated browser sessions, including Laravel Forge, PostHog, and Google Analytics administration.
  • No passwords, tokens, analytics keys, or other secrets are included in this report.

Relevant log location

C:\Users\joakl\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\08\19

I can provide relevant logs after reviewing them for private project information.

Request

Please investigate the Windows sandbox setup/orchestrator helper. In particular, could you confirm why the setup helper exits successfully before completing its expected initialization handshake and whether there is a supported repair or re-registration procedure that does not require resetting all local Codex state?

What steps can reproduce the bug?

Asking a work chat to do something that requires taking control of the browser

What is the expected behavior?

The work chat takes control of the browser

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Codex logs under C:\Users\joakl\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\08\19 and reproducing the Windows sandbox startup failure. Done means the setup helper completes its initialization handshake and Browser or Computer Use can return available tabs or windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.