openai / openai/codex

Codex browser control unavailable across secure browser, built-in Browser and Chrome

Open
#41,228 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug
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.820.9563.0

What subscription do you have?

Business

What platform is your computer?

Windows & IOS

What issue are you seeing?

Every Codex browser route is failing.

The ChatGPT Work secure browser repeatedly enters recovery and cannot reliably create, list, navigate or interact with tabs. The latest exact errors are:

CDP operation refresh tabs was superseded by browser recovery

CDP operation refresh tabs timed out after 20000ms

The built-in Browser fails with:

Browser is not available: iab

Backend discovery found no registered in-app Browser backend.

The Chrome extension detects and reads my authenticated tab but provides no interactive control. Codex cannot click, edit, save, run tests or download files.

What steps can reproduce the bug?

Feedback ID: 01a04594-5a75-71e1-8c7b-c99783482f69

What is the expected behavior?

Codex should reliably create, list and navigate tabs and provide interactive browser control through at least one supported browser route.

Additional information

Start a Codex Work chat and request a browser task.
The secure browser enters recovery and tab discovery times out.
Start a fresh conversation and clean browser session. The failure continues.
Attempt the documented recovery procedure. It does not resolve the fault.
Request the built-in Browser. It returns Browser is not available: iab.
Use Chrome with the Codex extension. Codex can read the page but cannot interact with it.

The app, browser and extension have been restarted or reinstalled roughly ten times.

I pay thousands of pounds annually for a Business subscription. These failures have persisted for several days, blocked live production work and wasted many hours.

Chats also fail to synchronise reliably with the Chrome side panel, long-running tasks repeatedly stall, and scheduled tasks have returned generic failure messages.

Please escalate this to engineering. Further instructions to reinstall or repeat the same recovery steps are not a resolution.

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 tracing the three reported browser routes: secure-browser recovery and CDP tab operations, built-in Browser backend discovery, and Chrome extension interaction. Use feedback ID 01a04594-5a75-71e1-8c7b-c99783482f69 and the documented recovery procedure as investigation context. Done means at least one supported route can reliably create, list, navigate, and interact with tabs.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.