Skip to content

Computer Use plugin fails after update due to missing @oai/sky package export for internal Windows client #28834

Description

@jeffmasc

What version of the Codex App are you using (From “About Codex” dialog)?

26.611.62324

What subscription do you have?

Enterprise

What platform is your computer?

Windows x64

What issue are you seeing?

After updating Codex, the computer-use plugin failed to initialize. The failure happened before any app automation action, during the plugin bootstrap.
The error was:

Package subpath './dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js' is not defined by "exports" in C:\Users\<user>\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_modules\@oai\sky\package.json

The file actually exists at:

C:\Users\<user>\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_modules\@oai\sky\dist\project\cua\sky_js\src\targets\windows\internal\computer_use_client_base.js

But package.json only exported the package root:

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

Meanwhile, computer-use-client.mjs imports this internal file directly:

import { WindowsComputerUseClientBase } from "@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js";
That causes Node to reject the import because the subpath is not listed in exports.

What steps can reproduce the bug?

  1. Use Codex App on Windows.
  2. Have the bundled computer-use plugin installed under:
    C:\Users\<user>\.codex\plugins\cache\openai-bundled\computer-use
    
  3. Attempt to use Computer Use.
  4. The plugin bootstrap fails with:
    Package subpath ... computer_use_client_base.js is not defined by "exports"
    

Observed local versions/paths:

computer-use plugin version before update: 26.611.61753
computer-use plugin version after update: 26.611.62324
cua_node runtime path: C:\Users\<user>\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117
@oai/sky version: 0.4.13

The issue remained relevant after the plugin updated to 26.611.62324, because the newer computer-use-client.mjs still imports the same internal @oai/sky path.

What is the expected behavior?

The computer-use plugin should initialize successfully without requiring users to patch files inside the local Codex runtime cache.

Either:

  1. @oai/sky/package.json should export the internal path used by computer-use-client.mjs, or
  2. computer-use-client.mjs should avoid importing a non-exported package subpath, or
  3. the bundled computer-use plugin and cua_node/@oai/sky runtime should be versioned together so incompatible cache combinations cannot occur.

Additional information

I was able to work around the issue locally by adding this exact export to:

C:\Users\<user>\AppData\Local\OpenAI\Codex\runtimes\cua_node\a89897d3d9baa117\bin\node_modules\@oai\sky\package.json
"./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 adding that export, computer-use initialized successfully and sky.list_apps() returned installed/running Windows apps.

This suggests the root cause is likely a packaging/export mismatch between the Codex App bundled computer-use plugin and the bundled @oai/sky runtime, rather than a Windows automation permission issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-useskillsIssues related to skillswindows-osIssues related to Codex on Windows systems

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions