openai / openai/codex

Browser plug in and chrome setting not working in the app

Open
#39,211 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug computer-use skills
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)?

0.148.0-alpha.15

What subscription do you have?

Pro

What platform is your computer?

uname -mprs

What issue are you seeing?

The bundled Browser, Chrome, and Computer Use plugins are installed and enabled. Mentioning @Browser, @Chrome, or @Computer injects the corresponding plugin skill into the task, but the live control interface does not attach. As a result, Codex cannot inspect or control either the in-app browser, Chrome, or macOS applications.

What steps can reproduce the bug?
  1. Open the existing Codex task.
  2. Mention @Chrome and request: “open my current Shopify tab and tell me the page title only.”
  3. Observe that the Chrome skill loads, but the browser-control tool is unavailable.
  4. Retry after tagging both the Chrome application and Chrome plugin.
  5. Mention @Browser; observe the same failure for the in-app browser.
  6. Mention @Computer; observe the same failure for Computer Use.
  7. Fully quit and reopen the ChatGPT desktop app and repeat.
What is the expected behavior?

Mentioning an enabled Browser, Chrome, or Computer Use plugin should attach its control interface so Codex can perform a read-only action, such as reading the current page title.

Additional information
  • The browser-control executable exists and responds to --help.
  • The configured trusted browser-client hash matches the installed Browser plugin file.
  • Browser, Chrome, and Computer Use are all marked enabled in the generated Codex configuration.
  • The app rewrites features.js_repl to false at startup. This setting is not documented in the public configuration reference and appears app-managed; manually changing it does not resolve the issue.
  • No Shopify content, credentials, cookies, or browser storage were inspected.

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

Reproduce the existing-task flow with @Chrome, @Browser, and @Computer, then inspect the browser-control executable and the generated Codex configuration, especially the app-managed features.js_repl rewrite. Trace where enabled plugins are attached to the live control interface and verify the trusted browser-client hash path. Done means each enabled plugin exposes its control interface and can complete a read-only page-title action.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.