Windows Codex App: Computer Use unavailable and /feedback command not available

Open 💬 3 comments Opened Jun 3, 2026 by Bruce-mo-ziwei

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

版本 26.601.21317 • 发布于 2026年6月3日

What subscription do you have?

ChatGPT Plus

What platform is your computer?

PS C:\Windows\system32> $([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" }) 所在位置 行:1 字符: 60 + $([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Env ... + ~~ 表达式或语句中包含意外的标记“$(”。 + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : UnexpectedToken

What issue are you seeing?

What issue are you seeing?

Windows Codex App latest version.

Problems:

  1. Settings → Computer Use shows: Computer Use plugin unavailable.
  2. Plugin marketplace search terms tried:
  • Computer Use
  • 电脑操控
  • Computer Control
  1. No Computer Use plugin found.
  2. Browser Use is available, but it only controls the in-app browser.
  3. /feedback command also shows “No command / 无命令”.

Expected need:
I need Windows desktop Computer Use for foreground control:

  • open Notepad
  • click Windows application windows
  • type text
  • save files
  • operate File Explorer / Calculator / normal desktop apps

This does not appear to be a project configuration issue, because the project directory works normally and Browser Use is visible, but Computer Use is unavailable.

What steps can reproduce the bug?

What is the expected behavior?

Computer Use should be available in the Windows Codex App.

Expected behavior:

  1. Settings → Computer Use should allow installing or enabling the Computer Use plugin.
  2. The assistant should have access to Computer Use after installation.
  3. Codex should be able to operate Windows foreground desktop apps through Computer Use, such as:
  • opening Notepad
  • typing text
  • saving a file
  • opening Calculator
  • operating File Explorer
  1. /feedback should be available from the composer, or there should be another visible in-app feedback route.

What is the expected behavior?

What is the expected behavior?

Computer Use should be available in the Windows Codex App.

Expected behavior:

  1. Settings → Computer Use should allow installing or enabling the Computer Use plugin.
  2. The assistant should have access to Computer Use after installation.
  3. Codex should be able to operate Windows foreground desktop apps through Computer Use, such as:
  • opening Notepad
  • typing text
  • saving a file
  • opening Calculator
  • operating File Explorer
  1. /feedback should be available from the composer, or there should be another visible in-app feedback route.

Additional information

Additional information

Environment:

  • OS: Windows
  • App: Codex App, latest version
  • Subscription: ChatGPT Plus
  • Workspace: Personal account
  • Region: Korea

Screenshots available:

  1. Settings → Computer Use showing “Computer Use plugin unavailable”.
  2. Plugin marketplace search result showing no Computer Use plugin.
  3. Browser Use visible in the plugin marketplace.
  4. /feedback showing “No command / 无命令”.

Related observations:

  • Browser Use is visible, but it only controls the in-app browser.
  • The requested use case requires desktop Computer Use, not Browser Use.
  • The project directory is not the problem; Codex can create and edit project files normally.
  • The issue appears related to account eligibility, workspace availability, regional availability, or bundled plugin availability/sync.

<img width="1278" height="676" alt="Image" src="https://github.com/user-attachments/assets/fddb39f7-dd9f-4da8-887f-258736c43f38" />
<img width="771" height="394" alt="Image" src="https://github.com/user-attachments/assets/c8fff8e5-cbd2-4678-af18-d5489171aed1" />
<img width="747" height="99" alt="Image" src="https://github.com/user-attachments/assets/a047fe28-42b0-4032-9092-a8049488b0dd" />

View original on GitHub ↗

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