Repository navigation
Windows desktop upgrade leaves openai-bundled marketplace partial, causing Browser/Computer Use unavailable #26501
Description
Summary
After recent Codex Windows desktop app upgrades/restarts, Browser and Computer Use repeatedly become unavailable or appear unavailable in settings. Local diagnostics show that Codex can leave the active bundled marketplace directory in a partial/corrupt state:
C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled
The active directory may contain only:
plugins\chrome\extension-host
and is missing:
C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled\.agents\plugins\marketplace.json
When this happens, CLI reports:
No plugins found in marketplace openai-bundled
while the plugin cache still contains installed Browser / Chrome / Computer Use plugin roots.
Environment
- OS: Windows
- Codex desktop app observed before update:
OpenAI.Codex_26.601.2237.0_x64__2p2nqsd0c76g0 - Codex desktop app after update:
OpenAI.Codex_26.602.3474.0_x64__2p2nqsd0c76g0 - CLI observed before update:
Codex Doctor v0.136.0-alpha.2 - CLI after update:
Codex Doctor v0.137.0-alpha.4 - Bundled plugin runtime observed after update:
26.602.30954 - Codex home:
C:\Users\dzr04\.codex
Impact
- Settings can show Browser or Computer Use unavailable after restart/update.
codex plugin list --marketplace openai-bundledreturns no plugins.- Computer Use native pipe can fail at startup with missing helper paths.
- Browser IAB may still be internally available, but marketplace/plugin state exposed to settings/CLI is inconsistent.
- Manual repairs are not durable across updates/restarts.
Evidence
codex doctor --summary reports config/auth/runtime loaded with no hard failures, e.g.:
15 ok · 1 idle · 3 notes · 2 warn · 0 fail degraded
But:
codex plugin list --marketplace openai-bundled
returns:
No plugins found in marketplace openai-bundled
Observed active marketplace path:
C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled
Observed contents:
plugins
Missing:
C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled\.agents\plugins\marketplace.json
Observed plugin cache still contains installed roots such as:
C:\Users\dzr04\.codex\plugins\cache\openai-bundled\browser\26.602.30954C:\Users\dzr04\.codex\plugins\cache\openai-bundled\chrome\latestC:\Users\dzr04\.codex\plugins\cache\openai-bundled\computer-use\26.602.30954
Relevant log messages observed include:
bundled_plugins_runtime_marketplace_written pluginCount=4 pluginNames=["browser","chrome","computer-use","latex"] targetMarketplaceRoot=C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled
Earlier version also produced:
marketplace 'openai-bundled' is already added from a different source; remove it before adding this source
Recent version produced:
computer-use notify config ensure finished platform=win32 reason=missing-helper-path status=skipped
computer-use native pipe startup failed errorMessage="Windows Computer Use helper paths are unavailable"
There were also file-operation failures during bundled marketplace rebuild:
EPERM: operation not permitted, rename '...\openai-bundled.staging-...' -> '...\openai-bundled'
Earlier runs also showed EBUSY around Chrome/extension-host files.
Additional observation
The Browser IAB backend itself can still be reachable. Using the Browser plugin client through node_repl, agent.browsers.get("iab") succeeded and listed the current in-app browser tab. This suggests the Browser backend may be running, while marketplace/plugin state is corrupted or unsynchronized.
Reproduction pattern
- Use Codex desktop app on Windows.
- Enable/use Browser and Computer Use.
- Let Codex desktop update, or restart Codex after update.
- Open settings for Browser / Computer Use.
- Browser or Computer Use may show unavailable.
codex plugin list --marketplace openai-bundledmay report no plugins.- Inspect
C:\Users\dzr04\.codex\.tmp\bundled-marketplaces\openai-bundled. - The directory may be partial and missing
.agents\plugins\marketplace.json.
Suspected root cause
The Codex desktop app appears to rebuild the bundled openai-bundled marketplace under .codex\.tmp\bundled-marketplaces. On Windows, this rebuild can be interrupted or blocked by file locks from extension-host.exe / native messaging host processes, leaving a partial active marketplace. Subsequent plugin/state reads treat openai-bundled as empty or invalid.
There also appears to be a startup ordering issue where Computer Use native pipe initialization can happen before the rebuilt marketplace and installed helper paths are available, causing missing-helper-path.
Workarounds tried
- Cleaning malformed TOML project headers.
- Removing invalid project-level
.codex/config.toml. - Reinstalling
browser@openai-bundled,chrome@openai-bundled, andcomputer-use@openai-bundled. - Removing custom fixed marketplace overrides.
- Killing stale
extension-host.exe. - Testing
CODEX_ELECTRON_ENABLE_WINDOWS_COMPUTER_USE=1. - Verifying Browser IAB directly with Browser plugin client.
Some workarounds temporarily restore functionality, but the issue recurs after updates/restarts.
Non-fixes / pitfalls
These should not be required and were not durable:
- Long-term overriding
[marketplaces.openai-bundled]to a custom fixed directory. - Relying on
openai-bundled-fixedas the primary marketplace. - Setting
SKY_CUA_SERVICE_PATHornotifytocodex-computer-use.exe.
Requested fix
Please investigate Codex desktop bundled marketplace rebuild on Windows:
- Ensure
.tmp\bundled-marketplaces\openai-bundledis updated atomically and never left as the active marketplace if staging/rename fails. - Detect and recover from partial active marketplace directories missing
.agents\plugins\marketplace.json. - Avoid deleting/uninstalling bundled plugin state based on a partial marketplace.
- Delay or retry Computer Use native pipe initialization until
computer-use@openai-bundledhelper paths are available. - Handle native messaging
extension-host.exefile locks during upgrade/rebuild.
Activity
github-actions commentedon Jun 5, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
kotodamaP commentedon Jun 11, 2026
I also hit a related Windows case and closed my separate report (#27493) as a likely duplicate/related issue.
Additional observation from my case, without local paths or private details:
So in my case the runtime appeared reachable, while plugin listing/UI reflection still made Computer Use look missing. That seems consistent with a bundled marketplace/plugin-state synchronization issue rather than the helper itself being entirely unavailable.
Orange1006mm commentedon Jun 11, 2026
Reproduced on a newer Windows desktop build with a deterministic lock owner and the same partial marketplace outcome.
Environment
OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g00.138.0-alpha.726.608.12217--no-startup-windowprocesshehggadaopoacecdllhhajmbjkdcmajgObserved sequence
After restoring the bundled marketplace and installing
browser,chrome, andcomputer-use, Settings briefly showed Browser and Computer Use normally.Codex startup reconciliation wrote a valid marketplace and the plugins appeared.
The browser extension started the native host from:
%CODEX_HOME%\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exeIn this build, the
chrome\latestjunction was recreated to point directly into the active marketplace:%CODEX_HOME%\.tmp\bundled-marketplaces\openai-bundled\plugins\chromeA later startup/focus reconciliation attempted to replace/remove that active marketplace while
extension-host.exewas running. Windows rejected the directory removal withEBUSY.Immediately afterward, Settings lost Browser and Computer Use. The active marketplace contained only
plugins\chrome,.agents\plugins\marketplace.jsonwas missing, andcodex plugin list --marketplace openai-bundled --available --jsonreturned empty arrays.Relevant log excerpt, with the user path redacted:
The lock owner was confirmed as
extension-host.exe, launched by Edge's Codex extension. Edge remained active in the background even when no visible browser window was open.Isolation result
With all Chromium processes and
extension-host.exestopped, restoring the marketplace made Browser and Computer Use remain visible through reconciliation. Reopening Edge allowed the native host to start and the failure recurred on a subsequent Codex reconciliation/restart.Manually redirecting
chrome\latestto the stable versioned cache temporarily avoided the lock, but Codex recreated the junction back to the active marketplace on startup, so this is not a durable workaround.This suggests the current implementation exposes the staging/active marketplace directory as the native host runtime path, then attempts to atomically replace that same directory while Windows has the executable mapped. The failure path leaves the marketplace partially materialized instead of retaining or rolling back to the previous valid snapshot.
Potential fixes appear to be:
latestto a directory that reconciliation later removes.johnsilvavlogs commentedon Jun 23, 2026
Additional Windows reproduction from a current build, with a narrower config-drift variant that looks like the same failure class.
Environment
10.0.26200OpenAI.Codex_26.616.9593.0_x64__2p2nqsd0c76g00.142.026.616.71553cua-node-0.0.2-20260620010411-120c650ffb83-windows-x64.zipSymptom
Settings > Computer use showed:
Key finding
This was not a missing Computer Use helper/runtime. The bundled plugin files were present, and the supported
computer-use-client.mjsbootstrap could reach the helper and list apps.Read-only runtime check before repair:
The broken layer was plugin/settings discovery from persisted config:
On this Windows host, those macOS absolute paths made the configured surfaces inconsistent:
The current user-level bundled marketplace did exist locally at:
and contained
browser,chrome,computer-use, andlatexplugin entries.Local repair that restored discovery
I updated only the stale host-specific paths in
config.toml:After repair:
Why this matters
This looks like the same broad class as the partial/stale bundled marketplace reports, but with a slightly different persistence bug: a Windows Codex install can retain macOS absolute paths in
config.toml, so the runtime can be healthy while Settings/CLI plugin discovery concludes that Computer Use is unavailable.Suggested product guard:
openai-bundledandnode_replagainst the current OS.computer-use@openai-bundledis discoverable from the active marketplace and thatnode_replresolves to the current platform runtime.zemeng5208 commentedon Aug 12, 2026
Disclosure: I maintain WinBridge Recovery, an independent Windows Codex Desktop recovery utility.
This is almost a direct match for the tool’s bundled-marketplace recovery path: the active
.codex\.tmp\bundled-marketplaces\openai-bundleddirectory is partial,marketplace.jsonis missing, while versioned plugin caches still exist and later reads treat the marketplace as empty.WinBridge Recovery resolves the currently installed official Codex package, validates the generated bundled marketplace and installed plugin/cache state, creates a rollback backup, and can rebuild the user-side marketplace/cache/pointer state when the active copy is incomplete or stale. It also checks related Chrome/native-host state because a locked extension host can be the event that leaves the marketplace half-written.
It does not modify WindowsApps or bypass product availability gates. So if the marketplace is intentionally reduced by a server-side feature decision, that is outside scope. But for the interrupted/partial local marketplace state described here, this is one of the clearest cases where the utility is intended to help.
MickeyWzt commentedon Aug 15, 2026
Fresh evidence from Store build
26.810.7004.0shows the partial/stale marketplace class still reproducing, alongside the same-name source conflict.sites,browser,chrome,computer-use,latex,deep-research, andvisualize.sites,browser,chrome,computer-use,latex, andvisualize.26.810.52044, while localchrome\lateststill targeted26.810.50856.chrome\26.810.52044\scripts\extension-ids.jsondid not exist..codex\.tmp\bundled-marketplaces\openai-bundledconflicted with a persisted stable source of the same marketplace name.The package itself was healthy, Store-signed, and physically installed on the system AppX volume. This occurrence is therefore separate from the earlier cross-volume protected-file copy trigger.
Full sanitized postmortem:
https://gist.github.com/MickeyWzt/416bd69fa28b59c65aaec37aed9b34d1
amirhossein-sadeghiyeh commentedon Sep 8, 2026
Newer Windows AppX data point from Codex Desktop
26.901.6511.0.Bundled marketplace reconciliation repeatedly failed while copying a bundled plugin manifest from the protected WindowsApps installation directory into the user-side staging marketplace.
Sanitized error shape:
The bundled Browser plugin files were present in the installed package. Restoring the matching Browser runtime files and registering a valid local marketplace snapshot allowed the Browser backend to start and complete a read-only navigation smoke test. This indicates that “plugin unavailable” can result from an incomplete marketplace snapshot rather than missing package contents.
Suggested behavior:
This workaround was version-specific and should not be treated as a supported repair.