›_ Codex Issues
Codex Issues / #40768

Windows Computer Use plugin is repeatedly restored as version 26.611.62324 after clearing its cache and restarting Codex.

Open 💬 1 comment Opened Aug 26, 2026 by millerspeller3311-arch

Windows Computer Use plugin is repeatedly restored as version 26.611.62324 after clearing its cache and restarting Codex.

The plugin bootstrap consistently fails with:

Module not found:
@oai/sky/dist/project/cua/sky_js/src/targets/windows/internal/computer_use_client_base.js

Reproduction:

  1. Remove or rename:

C:\Users\K\.codex\plugins\cache\openai-bundled\computer-use\26.611.62324

  1. Restart Codex.
  2. Codex downloads the same version again.
  3. Calling Computer Use fails with the same missing-module error.

This appears to be a version mismatch between the server-distributed Computer Use plugin and the @oai/sky runtime bundled with the current Windows Codex desktop app.

View original on GitHub ↗

1 Comment

zemeng5208 · 2 days ago

This looks like a concrete Windows local-state/version-drift case rather than only a generic Computer Use failure.

I maintain WinBridge Recovery: https://github.com/zemeng5208/winbridge-recovery

For this specific symptom, WinBridge may help diagnose/recover the local bundled plugin layer by checking the openai-bundled/computer-use cache, active version/latest state, bundled marketplace staging, and the local CUA runtime/helper paths so you can tell whether the machine is actually stuck on a stale or partially staged plugin version.

The important limitation here is the behavior you already observed: if clearing the local cache causes Codex to download 26.611.62324 again, and the regenerated local state is internally consistent, then the remaining mismatch is likely upstream distribution/version selection or a plugin/runtime compatibility problem. WinBridge cannot change what version the service/desktop build chooses to re-materialize, and it cannot guarantee a fix for an upstream @oai/sky export mismatch.

So I would use it mainly to verify whether there is still recoverable local cache/latest/marketplace drift; if those layers are healthy and Codex keeps restoring the same incompatible version, that is strong evidence the durable fix needs to be in Codex's version-selection/bundling path.