openai / openai/codex

Windows desktop: Chrome plugin missing from Plugins page; `js_repl` is forced back to `false` on startup; sessions get EPERM when connecting to the browser pipe

Open
#40,923 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment:

  • OS: Windows 11, build 10.0.26200.0
  • Codex Desktop: 26.820.60940 (Microsoft Store; reproduced both before and after reinstall)
  • Chrome: 151.0.7922.174
  • Chrome extension (ChatGPT/Codex): installed; native messaging host com.openai.codexextension present; extension-host.exe running

Summary:
After a Microsoft Store update/reinstall, the Chrome plugin (and other openai-bundled plugins) is missing from the Plugins page, even though the plugin is installed and enabled at the config/CLI level. Reinstalling the app from the Store does not fix it.

Steps to reproduce:

  1. Install/update Codex Desktop on Windows from the Microsoft Store.
  2. Open the Plugins page and search for "Chrome" (also try switching marketplace sources, e.g. OpenAI Bundled).
  3. Chrome / Browser / Computer Use bundled plugins do not appear.

What I verified:

  • codex plugin list shows chrome@openai-bundled installed, enabled 26.820.60940.
  • ~/.codex/config.toml contains [plugins."chrome@openai-bundled"] enabled = true and a valid [marketplaces.openai-bundled].
  • The bundled marketplace staging (~/.codex/.tmp/bundled-marketplaces/openai-bundled) was rebuilt and versions match the cache.
  • Chrome extension + native host are present; extension-host.exe is running.
  • Removing/re-adding the plugin via CLI fails with "Access is denied" while the app is running (file lock), and the app's own Plugins UI offers no way to manage the bundled plugin.

Additional blockers:

  1. ~/.codex/config.toml has [features] js_repl = false. Editing it to true while Codex is fully closed succeeds, but Codex rewrites it back to false on the next startup (observed at 2026-08-27 00:22:20 and 00:41:58). Because of this, the mcp__node_repl__js tool is not exposed to sessions and the Chrome/Browser skills cannot execute.
  2. Attempting to connect to the browser control pipe from a session returns EPERM (access denied). Sessions run in the sandboxed command runner and cannot reach the browser native host.

Expected behavior:

  • openai-bundled plugins (Chrome / Browser / Computer Use) should be listed in the Plugins page on Windows.
  • js_repl should not be silently reset on startup.
  • Sessions should be able to connect to Chrome through the installed extension.

Related issues: #22598, #25878, #26501

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 three reported failures on Windows 11: the Plugins page and codex plugin list, startup handling of ~/.codex/config.toml, and browser-pipe access from a session. Trace the bundled marketplace/plugin discovery, js_repl startup handling, and native messaging permissions; done means bundled plugins appear, js_repl remains enabled, and sessions can connect without EPERM.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, desktop, operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.