Computer Use bundled plugin is usable on Windows but not reflected in plugin list/UI

Resolved 💬 3 comments Opened Jun 11, 2026 by kotodamaP Closed Jun 11, 2026

Summary

On Windows, the bundled Computer Use plugin appears to be available at runtime, but it is not reflected in the plugin list / plugin UI.

This makes it look like the plugin disappeared or is not installed, even though the Computer Use runtime can still be reached.

No local paths, app names, account details, screenshots, database contents, or private configuration are included here.

Observed behavior

  • codex plugin list does not show the bundled Computer Use plugin.
  • The user-facing plugin state appears as if Computer Use is not reflected/enabled.
  • However, the Computer Use skill/runtime files are present in the bundled plugin cache.
  • A lightweight Computer Use runtime check can successfully connect to the Windows helper and list installed apps.

Expected behavior

  • If Computer Use is available and usable in the current Codex Desktop session, it should be reflected consistently in the plugin list / plugin UI.
  • If bundled plugins are intentionally hidden from codex plugin list, the UI or CLI should make that distinction clear.
  • If Computer Use is not supposed to be available, the runtime should not be exposed as usable.

Why this is confusing

The current state has mixed signals:

  • Runtime: Computer Use works.
  • Plugin reflection/listing: Computer Use appears missing.

This makes it hard to tell whether the issue is a local installation problem, a disabled plugin, or a UI/plugin-registry bug.

Suggested checks

Codex could validate and surface:

  • Whether bundled plugins are intentionally omitted from codex plugin list.
  • Whether Computer Use is enabled for the current Desktop session.
  • Whether the bundled Computer Use cache is present.
  • Whether the Windows helper can be reached.
  • A clear status such as available, disabled, not installed, or bundled but hidden from plugin list.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗