Computer Use on Windows fails to initialize due to non-exported @oai/sky internal subpath

Summary

On Windows, the bundled Computer Use plugin fails during initialization before any app/window can be listed. This blocks using Computer Use with desktop apps such as Thunderbird.

Observed error

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\<runtime-hash>\bin\node_modules\@oai\sky\package.json

Environment observed

• OS: Windows
• Codex desktop/app session with bundled Computer Use plugin
• Computer Use plugin cache version observed after restart: openai-bundled/computer-use/26.611.62324
• Runtime package observed after restart: @oai/sky version 0.4.13
• Previous runtime before restart showed the same error with @oai/sky version 0.4.10

Reproduction steps

1. Start a Codex session on Windows with the Computer Use plugin available.
2. Load the bundled Computer Use client from:

.../plugins/cache/openai-bundled/computer-use/<version>/scripts/computer-use-client.mjs

1. Run the documented bootstrap flow:

const { setupComputerUseRuntime } = await import(".../scripts/computer-use-client.mjs");
await setupComputerUseRuntime({ globals: globalThis });
await sky.list_apps();

Expected behavior

Computer Use initializes and sky.list_apps() returns installed/running Windows apps.

Actual behavior

Initialization fails before sky.list_apps() can run because computer-use-client.mjs imports:

@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js

but @oai/sky/package.json only exports the package root:

"exports": {
  ".": "./dist/project/cua/sky_js/src/index.js"
}

Likely cause

The bundled Computer Use plugin imports an internal @oai/sky subpath that is not exposed through the package exports map. This appears to be a packaging/API compatibility issue between the Computer Use plugin and the bundled @oai/sky runtime.

Notes

Restarting Codex refreshed the plugin/runtime cache but did not resolve the issue. The failure still occurs before targeting any specific desktop app, so this is not app-specific.