Windows Store Codex: Chrome backend not registered and Computer Use native pipe missing
Summary
On Windows Store Codex, both bundled Chrome control and Computer Use are installed/enabled but do not become available inside Codex sessions.
- Chrome extension is installed and enabled.
- Native messaging manifest is valid.
extension-host.exestarts.agent.browsers.list()returns an empty array.- Computer Use plugin is installed/enabled in Codex UI, but the session receives no native pipe (
nodeRepl.nativePipeis absent,SKY_CUA_NATIVE_PIPE_DIRECTORYis absent). setupComputerUseRuntime()fails with native pipe missing / os error 2.
This looks like bundled plugin/native helper activation is broken for this Windows Store install.
Environment
- OS: Windows
- Codex app: Microsoft Store / WindowsApps package
- Codex package path:
C:\Program Files\WindowsApps\OpenAI.Codex_26.609.3341.0_x64__2p2nqsd0c76g0\app\Codex.exe - Codex AppID:
OpenAI.Codex_2p2nqsd0c76g0!App - OpenAI bundled plugin version:
26.609.30741 - Chrome plugin version:
26.609.30741 - Computer Use plugin version:
26.609.30741 - Codex Chrome Extension:
1.1.5_0 - Chrome extension ID:
hehggadaopoacecdllhhajmbjkdcmajg - Chrome profile:
Default
Chrome diagnostics
check-extension-installed.js --json reports:
{
"extensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
"selectedProfileDirectory": "Default",
"installed": true,
"enabled": true,
"profiles": [
{
"profileDirectory": "Default",
"installed": true,
"registered": true,
"enabled": true,
"disabled": false,
"versions": ["1.1.5_0"],
"selected": true
}
],
"exitCode": 0
}
check-native-host-manifest.js --json reports:
{
"expectedHostName": "com.openai.codexextension",
"actualHostName": "com.openai.codexextension",
"expectedExtensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
"expectedOrigin": "chrome-extension://hehggadaopoacecdllhhajmbjkdcmajg/",
"exists": true,
"nameMatches": true,
"hasExpectedOrigin": true,
"registryMatchesManifestPath": true,
"correct": true,
"problem": null
}
The manifest points to:
C:\Users\<user>\.codex\plugins\cache\openai-bundled\chrome\latest\extension-host\windows\x64\extension-host.exe
extension-host.exe has been observed running and responding.
However, from the Chrome browser client runtime:
{
"chrome": {
"browsers": []
}
}
So agent.browsers.list() returns [], and agent.browsers.get("extension") is unavailable.
Computer Use diagnostics
Computer Use is shown as installed/enabled in the Codex UI ("Control Windows apps from Codex", version 26.609.30741), but the current session receives no native pipe:
{
"nodeReplKeys": [
"cwd",
"emitImage",
"env",
"homeDir",
"requestMeta",
"setResponseMeta",
"tmpDir",
"write"
],
"hasNativePipe": false,
"envKeys": [],
"skyPipe": null,
"hasConfig": false
}
Calling Computer Use runtime fails:
Computer Use native pipe is unavailable: Error: failed to connect native pipe:
Не удается найти указанный файл. (os error 2)
Earlier, before applying a local workaround, computer-use-client.mjs also failed with:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath
'./dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js'
is not defined by "exports" in ...\node_modules\@oai\sky\package.json
The file exists physically, but the package exports only ".". I locally patched the import to a direct file:///... URL to continue diagnostics; after that, the failure moved to missing native pipe.
Reproduction steps
- Install Codex from Microsoft Store on Windows.
- Enable/install bundled
ChromeandComputer Use. - Install and enable the Codex Chrome Extension in Chrome profile
Default. - Start/restart Codex and Chrome.
- In a Codex session, run Chrome browser client setup and call
agent.browsers.list(). - In the same session, inspect
nodeRepl.nativePipe/nodeRepl.env.SKY_CUA_NATIVE_PIPE_DIRECTORY, then trysetupComputerUseRuntime().
Expected
- Chrome backend should register and appear in
agent.browsers.list(). - Computer Use session should have
nodeRepl.nativePipeor a validSKY_CUA_NATIVE_PIPE_DIRECTORY. sky.list_apps()should work and list Windows apps.
Actual
agent.browsers.list()returns[].nodeRepl.nativePipeis absent.SKY_CUA_NATIVE_PIPE_DIRECTORYis absent.setupComputerUseRuntime()fails with native pipe os error 2.
Workarounds attempted
- Reinstalled / re-enabled Codex Chrome Extension.
- Verified Chrome extension is installed and enabled.
- Verified native messaging manifest is valid.
- Fully restarted Codex and Chrome multiple times.
- Killed/restarted
extension-host.exe. - Reset bundled plugin cache by renaming
.codex\plugins\cache\openai-bundled. - Let Codex rebuild bundled marketplace/cache.
- Copied Store/WindowsApps helper binaries into
%LOCALAPPDATA%\OpenAI\Codex\binand restarted. - Repaired a broken
chrome\latestjunction/cache target manually. - Confirmed Computer Use appears enabled in Codex UI.
None of these made Chrome or Computer Use available inside the session.
Notes
This resembles other recent Windows issues where:
- Chrome extension/native host is installed but no browser backend registers.
- Computer Use is enabled but the session lacks native pipe metadata.
- Windows Store / WindowsApps packaging appears to interact badly with native helper discovery or pipe injection.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I have a very similar Windows Store Codex case and filed #27866 before seeing this issue.
Additional data point:
OpenAI.Codex 26.609.3341.0openai-bundled/chrome/26.609.30741142.0.7444.1631.1.5_0Defaultextension-host.exethrough native messaging.agent.browsers.list()returns only the Codex in-app browser (type: "iab") in my case, rather than an empty list.agent.browsers.get("extension")still fails withBrowser is not available: extension.So this looks like the same Windows Store / bundled helper activation issue, except the in-app browser backend is registered while the Chrome extension backend is not.
One extra diagnostic note: on Korean Windows,
reg query /vecan show the default registry value localized as(기본값), and one diagnostic path appeared to misread that as the key being missing. A directnode scripts/check-native-host-manifest.js --jsonrun reports the manifest as correct, so this may be a separate diagnostics/localization issue rather than the root cause.Additional reproduction on a newer Windows Store Codex build.
Environment:
10.0.26200,ko-KROpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g00.140.0-alpha.2openai-bundled/computer-use/26.609.41114@oai/sky:0.4.10computer-use@openai-bundledis enabled in~/.codex/config.tomlcomputer_use\\.\pipe\codex-computer-use-...Observed failure 1: documented Computer Use bootstrap fails before contacting the helper:
The bundled plugin imports:
but
@oai/sky/package.jsonexports only:The target file exists, and direct file URL import works and exposes
WindowsComputerUseClientBase.Observed failure 2: for diagnosis only, I copied
computer-use-client.mjsto a workspace-local file and changed only that import to a file URL. That bypassed the exports error, but bootstrap then failed with:Current Node REPL inspection from the affected session:
So this still appears two-layered on
26.609.4994.0/ plugin26.609.41114:computer-use-client.mjsimports a non-exported@oai/skypackage subpath.nodeRepl.nativePipe/ approval bridge expected byNativePipeComputerUseTransport.create().codex doctor --jsonfrom the accessible user-local CLI reportsconfig.load: okand feature flags includecomputer_use;network.websocket_reachability: ok; installation is locally consistent, though PATH contains multiple Codex entries. Running the MSIX-bundledapp/resources/codex.exedirectly fromC:\Program Files\WindowsApps\...is blocked by Windows access control, but the user-local CLI path runs.Impact: Computer Use is shown as installed/enabled and documented as available for Windows desktop app control, but the bundled bootstrap path is unusable in this Windows Codex App session. I did not modify bundled plugin/runtime files; the patched file was only a local diagnostic copy.
I maintain WinBridge Recovery, an independent Windows Codex Desktop local-state diagnostic/recovery utility: https://github.com/zemeng5208/winbridge-recovery
This thread has two layers that are worth separating. The Chrome/Computer Use entries can be installed and enabled while the active session still lacks the expected extension backend / privileged
nodeRepl.nativePipe; separately, one reproduction shows the bundledcomputer-use-client.mjsimporting an@oai/skysubpath that the bundled package does not export.WinBridge can help with the first when it is caused by mixed local state: active
CODEX_HOME, bundled marketplace, concrete plugin cache/latest,cua_node/node_repl, and native-host paths are checked against the official installed package as one set, with backup and verification before local repair. It also avoids treating localizedreg queryoutput as proof that the registry entry is absent.It cannot legitimately fix an internally incompatible official plugin/package pair or manufacture the privileged native pipe if Desktop never provisions it. If those official resources are mutually inconsistent, the correct result is an upstream diagnosis rather than patching package code.
If anyone with either reproduction tries WinBridge, please record whether it was ✅ fixed, 🟡 local state repaired but backend still missing, or ❌ unchanged at https://github.com/zemeng5208/winbridge-recovery/issues/4. That distinction is exactly the field data I am trying to collect.
Update from the original reporter:
This appears to be fixed for my machine now.
I originally filed this against the Windows Store Codex
26.609.xbuilds, where the Chrome extension/native host was installed but the Chrome backend did not register, and Computer Use was enabled in the UI but the session had no usable Computer Use runtime/pipe.As of my current Windows Store Codex install:
OpenAI.Codex 26.810.4967.026.810.41047agent.browsers.list()now returns both:extensionbackend@oai/skysky.list_apps()succeeds and returns Windows apps/windowsI did not use WinBridge Recovery for this current working state. The local workaround documented earlier around copying/registering a user bundled marketplace is not what the current
config.tomlis using;openai-bundledis currently sourced from the normal.codex\.tmp\bundled-marketplaces\openai-bundledpath.So for my original reproduction, this looks fixed by a later Codex Desktop / bundled plugin update rather than by the old local workaround.
I have not tested whether older
26.609.xbuilds are still broken, so this may still be useful as historical diagnostics for users stuck on those builds.Closing this from my side since the original reproduction no longer reproduces on my current build.