Computer Use plugin fails on Windows due to @oai/sky package subpath not exported
Summary
The bundled Computer Use plugin fails during its documented bootstrap on Windows before sky.list_apps() can run. The failure is a Node package exports error from the bundled @oai/sky runtime.
Environment
- OS: Windows NT 10.0.26200.0
- PowerShell: 7.5.5
- .NET runtime visible to PowerShell: 9.0.14
- Codex bundled plugin:
openai-bundled/computer-useversion26.611.61753 - Bundled
@oai/skyruntime observed:0.4.13 - A second local
cua_noderuntime with@oai/sky0.4.10shows the same packageexportsshape
Reproduction
Using the plugin-documented bootstrap:
const { setupComputerUseRuntime } = await import("<plugin-root>/scripts/computer-use-client.mjs");
await setupComputerUseRuntime({ globals: globalThis });
globalThis.apps = await sky.list_apps();
Actual result
Bootstrap fails immediately 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 <cua_node-runtime>/bin/node_modules/@oai/sky/package.json
The stack starts at Node ESM resolution / package exports resolution before any Windows helper call is made.
Local findings
The plugin file imports an internal subpath directly:
import { WindowsComputerUseClientBase } from "@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js";
The bundled @oai/sky/package.json contains only:
"exports": {
".": "./dist/project/cua/sky_js/src/index.js"
}
The target file does exist on disk at:
@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js
So this appears to be an export-map/package-boundary mismatch rather than a missing compiled file.
There is also a nearby bundled file:
@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client.js
which imports ./computer_use_client_base.js relatively and exports WindowsComputerUseClient. That may be the intended public or package-internal entry point, but it is also not exported through package.json today.
Expected result
The documented Computer Use bootstrap should complete successfully on Windows and allow sky.list_apps() to return a list of apps/windows.
Suggested fix direction
Either:
- Export the required Windows internal entry point(s) from
@oai/sky/package.json, or - Change
computer-use-client.mjsto import from a supported public@oai/skyentry point, or - Bundle the required Windows client base code inside the plugin so it does not cross the
@oai/skypackage exports boundary.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I can reproduce this on the current Microsoft Store Codex package after self-update:
The failure is the same ERR_PACKAGE_PATH_NOT_EXPORTED for:
./dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.jsThis also appears in the installed Store package payload, not only my extracted cache, so a normal Repair/Reinstall would likely restore the same broken pairing.
As a diagnostic workaround only, I backed up the runtime @oai/sky package.json and added this export:
After resetting the JS kernel,
sky.list_apps()returned 40 apps and Computer Use could control Windows apps (Explorer, Calculator, System Information). The workaround proves the import/export mismatch, but I do not want to keep running a patched Codex because app/plugin self-updates may overwrite it or create other issues.I can reproduce the same Computer Use bootstrap failure on Windows after updating Codex and restarting the app.
Environment from this machine:
OpenAI.Codex_26.611.8604.0_x64__2p2nqsd0c76g0openai-bundled/computer-useversion26.611.62324@oai/skyruntime version:0.4.13@oai/skyruntime path:C:\Users\fioei\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_modules\@oai\skyC:\Users\fioei\.codex\plugins\cache\openai-bundled\computer-use\26.611.62324Exact error:
Additional local findings:
...\@oai\sky\dist\project\cua\sky_js\src\targets\windows\internal\computer_use_client_base.js.file://URL succeeds and exposesWindowsComputerUseClientBase.@oai/sky/package.jsononly exports.:So this still appears to be a package export-map mismatch: the file is present, but the first-party Computer Use plugin imports it through a package subpath that Node refuses.
I also observed that, in this failing thread, the JS runtime did not expose the privileged native pipe fields Computer Use expects (
nodeRepl.nativePipewas absent andSKY_CUA_NATIVE_PIPE_DIRECTORYwas not present), but the package-export failure happens first, before any Windows helper/native-pipe call can run.I can confirm the same issue on Windows.
Computer Use is available as a bundled plugin, but it fails during initialization before it can connect to the desktop or run
sky.list_apps().Environment observed here:
openai-bundled/computer-useversion26.611.62324cua_node/a89897d3d9baa117@oai/skyExact failure:
I’m seeing the same issue on Windows.
Computer Use is unavailable in Codex settings, and the documented bootstrap fails before
sky.list_apps()with the same@oai/skypackage exports error:Package subpath './dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js' is not defined by "exports" in ...\@oai\sky\package.jsonI also reported this through in-app feedback with Feedback ID:
019ed340-09f1-7783-b40b-b3f08f9c4147Browser tools still work for me: in-app browser and Chrome control can open pages and take screenshots. The failure appears isolated to Computer Use.
I used Codex Version 26.616.30709 • Released 2026/06/19