Computer Use plugin fails after Codex update because @oai/sky package exports omit internal Windows client subpath
Open 💬 7 comments Opened Jun 13, 2026 by CarlonX1
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
After a Codex desktop update, the bundled Computer Use plugin fails to initialize on Windows. The plugin imports an internal @oai/sky subpath that exists on disk, but is not declared in @oai/sky/package.json exports.
Adding the missing export manually restores Computer Use.
Environment
- OS: Windows
- Codex app:
26.609.4994.0 - Computer Use plugin:
26.608.12217 - Runtime:
%LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node\789504f803e82e2b @oai/sky:0.4.10- Codex was not running as administrator
- Computer Use was enabled in Codex settings
Error
When initializing Computer Use through the plugin's documented client:
const { setupComputerUseRuntime } = await import(
"file:///%USERPROFILE%/.codex/plugins/cache/openai-bundled/computer-use/26.608.12217/scripts/computer-use-client.mjs"
);
await setupComputerUseRuntime({ globals: globalThis });
it fails with:
Package subpath './dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js'
is not defined by "exports" in
%LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node\789504f803e82e2b\bin\node_modules\@oai\sky\package.json
Observed details
The target file exists:
%LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node\789504f803e82e2b\bin\node_modules\@oai\sky\dist\project\cua\sky_js\src\targets\windows\internal\computer_use_client_base.js
But package.json only exports:
"exports": {
".": "./dist/project/cua/sky_js/src/index.js"
}
Workaround
Adding this export fixes the issue:
"exports": {
".": "./dist/project/cua/sky_js/src/index.js",
"./dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js": "./dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js"
}
After applying the workaround, sky.list_apps() succeeds and Computer Use can enumerate Windows apps.
Expected behavior
Computer Use should initialize without manually editing the bundled @oai/sky/package.json.
Actual behavior
Computer Use fails immediately during runtime setup because Node blocks the internal subpath import.
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Confirmed the same root cause on a newer bundled Computer Use build.
Additional environment where this reproduces:
0.125.026.609.41114computer-use@openai-bundled, version26.609.41114cua-node-0.0.1-20260609000952-8714bea94049-win32-x64.zip24.14.0@oai/sky:0.4.10I also tested reinstalling the
computer-use@openai-bundledplugin cache from the bundled marketplace source. Reinstalling the plugin alone does not fix the issue; with the original@oai/sky/package.jsonexport map restored, the sameERR_PACKAGE_PATH_NOT_EXPORTEDerror reproduces.The local workaround that restores functionality is the same one described here: add the missing export for
./dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.jsto the bundled@oai/sky/package.json.After applying that local export-map workaround and restarting the JS runtime, lightweight Computer Use checks passed:
I opened #28159 with the same findings before seeing this issue; I am closing that one as a duplicate of this issue.
Minor correction to the validation snippet in my previous comment: the intended values were:
deepImportExports:[WindowsComputerUseClientBase]appCount:40runningAppCount:6windowCount:6The important point is unchanged: plugin-cache reinstall alone reproduced the original export error, while adding the missing
@oai/skysubpath export restored Computer Use initialization.I can also confirm this on Windows Codex Desktop with:
openai-bundled/computer-use/26.609.41114@oai/sky:0.4.10cua_noderuntime hash observed locally:789504f803e82e2bThe failure was the same
ERR_PACKAGE_PATH_NOT_EXPORTEDerror for:The target file existed inside the bundled
@oai/skypackage, butpackage.jsononly exported the package root.I verified locally that adding this export entry restored Computer Use initialization:
After restarting the JS runtime,
sky.list_apps()succeeded again.Confirming this still reproduces on a newer Windows Codex Desktop Computer Use bundle.
Environment observed locally:
computer-use@openai-bundled, cache path%USERPROFILE%\.codex\plugins\cache\openai-bundled\computer-use\26.609.71450@oai/sky:0.4.10cua_noderuntime hash:789504f803e82e2bFailure during the supported Computer Use bootstrap:
The local workaround was to add the missing subpath export to
%LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node\789504f803e82e2b\bin\node_modules\@oai\sky\package.json:After resetting the JS runtime and rerunning the supported
computer-use-client.mjsbootstrap, Computer Use initialized successfully.sky.list_apps()returned the target Windows app/window, and a real input sequence sent through Computer Use to theGothic 1 Remakewindow worked.So the issue does not appear limited to the earlier
26.609.41114/26.609.30741plugin builds; it also affects26.609.71450until the missing@oai/skyexport is present.Still reproduces after the 2026-06-17 Codex update.
Environment:
Test performed:
Actual result:
Observed package.json still only exports:
The target file exists on disk, but the subpath is still not exported. So the Computer Use bootstrap still fails before it can reach any Windows helper/native pipe logic.
Still reproduces on the latest Codex Desktop I have available today (2026-06-18), and the local evidence matches this issue.
Environment:
OpenAI.Codex_26.611.8604.0_x64__2p2nqsd0c76g0openai-bundled/computer-use/26.611.62324a89897d3d9baa11724.14.0@oai/sky:0.4.13Current
@oai/sky/package.jsonexport map is still only:The bundled Computer Use client still imports the unexported internal subpath:
Rechecking the supported bootstrap/import path fails immediately with:
I also checked the native pipe side because Computer Use is still unavailable after reinstalling/restarting:
config.tomlhasSKY_CUA_NATIVE_PIPE=1and a configuredSKY_CUA_NATIVE_PIPE_DIRECTORYcodex-computer-use.exeexists locally; sha256F2B2F56FCD1699B0FA32DEC3214A56A1D36B937A2ECF58CC822AB4A904551E03nodeRepl.nativePipeis stillundefinednodeRepl.configisundefinednodeRepl.createElicitationisundefinednodeRepl.envis empty:[]So this still looks like a bundled plugin/runtime integration problem rather than a per-app permission issue. The exports mismatch blocks Computer Use bootstrap first; even after that, this environment also shows the missing nativePipe exposure described in related Windows reports.