openai / openai/codex

Chrome enabled but missing from @ menu; browser tool startup fails

Open
#46,476 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug tool-calls
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

Not applicable—using ChatGPT desktop app 26.908.70816, build 9275

What subscription do you have?

Pro

Which model were you using?

gpt-6-astra high

What platform is your computer?

macOS 26.6.2 (25G83), Apple Silicon. uname -mprs: Darwin 25.6.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Not applicable—ChatGPT desktop app

Codex doctor report
Not collected; issue occurs through the desktop app’s browser integration
What issue are you seeing?

Chrome browser integration previously worked in an ongoing Codex conversation inside the ChatGPT desktop app. After a browser tool timeout, subsequent connection attempts began failing.
Chrome is enabled under Settings → Computer Use, but Chrome does not appear in the @ menu in new chats.

The assistant's browser-tool startup returns: Importing module "node:process" is not allowed in node_repl

What steps can reproduce the bug?

Uploaded thread: 01a0a593-23dc-7772-96d5-ccf21b39ea54

What is the expected behavior?

Expected:
Chrome appears in the @ menu, and the assistant can connect to Chrome.

Actual:
Chrome is missing from the menu, and the existing conversation cannot
initialize its browser tools.

Additional information

Troubleshooting already performed:

  • Restarted Chrome.
  • Restarted the ChatGPT desktop app.
  • Opened new chats and a new Chrome session.
  • Confirmed Chrome is enabled in Computer Use.
  • Read-only diagnostics confirmed Chrome is running, the extension is
    installed and enabled, and the native-host registration is valid.

Environment:

  • ChatGPT desktop app: 26.908.70816, build 9275
  • macOS: 26.6.2, build 25G83
  • Architecture: Apple Silicon / arm64
  • Last observed extension version: 1.26.901.11451_0

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 reproducing the browser integration failure in the ChatGPT desktop app using the uploaded thread 01a0a593-23dc-7772-96d5-ccf21b39ea54 and the reported node_repl error. Trace the startup path that rejects node:process; done means Chrome appears in the @ menu and browser tools connect successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, node.js
Domain
desktop, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.