[Windows] Computer Use fails with spawn EPERM after app restores AppData runtime paths

Open 💬 1 comment Opened Aug 6, 2026 by kurtsmith5150-cmyk
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

On Windows, the bundled Computer Use plugin loads @oai/sky, but the first desktop call fails with spawn EPERM. As a result, Codex cannot list apps or inspect any Windows/NinjaTrader windows.

Environment

  • Windows desktop app (Microsoft Store package)
  • Codex package: OpenAI.Codex_26.730.8199.0_x64
  • Computer Use plugin: 26.730.61639
  • @oai/sky: 0.6.2
  • Bundled runtime ID: cua_node\fb8898c05a62885e

Steps to reproduce

  1. Install and enable the bundled Computer Use plugin.
  2. Restart the Codex desktop app.
  3. Initialize the documented package entry point and call:
const { sky } = await import("@oai/sky");
await sky.list_apps();

Actual behavior

The call fails immediately:

spawn EPERM

During earlier package resolution attempts, the runtime also reported:

Error: EPERM: operation not permitted, lstat 'C:\Users\User\AppData\Local\OpenAI\Codex'

The desktop app writes these Computer Use paths into %USERPROFILE%\.codex\config.toml:

  • mcp_servers.node_repl.command
  • NODE_REPL_NODE_MODULE_DIRS
  • NODE_REPL_NODE_PATH
  • NODE_REPL_TRUSTED_CODE_PATHS
  • CODEX_CLI_PATH

They point beneath:

C:\Users\User\AppData\Local\OpenAI\Codex

I copied the bundled Computer Use runtime to a normal user-readable directory and updated the configuration. The package could then be resolved from that location, but restarting the desktop app rewrote the node-repl command and environment values back to the inaccessible AppData runtime paths. The next sky.list_apps() call again failed with spawn EPERM.

Expected behavior

sky.list_apps() should start the bundled Windows Computer Use helper and return the available applications/windows. Computer Use should remain functional after restarting the desktop app.

Additional notes

The bundled files are also present under the Microsoft Store WindowsApps package. This appears to be a mismatch between the runtime paths persisted by the desktop app and the paths that the sandboxed Computer Use process is permitted to resolve/execute.

No screenshots or personal application content are attached.

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 21 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #37284
  • #37272
  • #37029
  • #37102

Powered by Codex Action