codex - 💡(How to fix) Fix Feature request: Full Computer Use support for Codex Desktop on Windows [1 participants]

What variant of Codex are you using?

Codex Desktop App on Windows, with WSL2 / PowerShell workflows. Browser Use is available, but full native Windows desktop Computer Use is not available.

What feature would you like to see?

I would like Codex Desktop on Windows to support full native Computer Use, similar to the macOS Computer Use workflow.

Today, Codex Desktop on Windows is already useful for projects, Git, Browser Use, terminal workflows, PowerShell, and WSL2. However, Browser Use only controls the in-app browser. It does not allow Codex to inspect or operate the actual Windows desktop, native Windows applications, settings dialogs, GUI tools, installers, IDE windows, or other non-browser workflows.

For many developers, Windows is the primary workstation. In my case, I use Windows for daily work and WSL2 for Linux development. I also work with remote Linux systems, terminal tools, Git workflows, browser dashboards, and desktop applications. The current Windows Codex App is helpful, but the missing full Computer Use support means I would need to buy and maintain a separate Mac only to access this workflow.

I actually tried using a Mac mini for this purpose, but the platform switch was uncomfortable for my existing workflow: keyboard behavior, mouse behavior, copy/paste habits, window management, monitor setup, and general daily usage were all friction points. I would strongly prefer to keep using my Windows workstation and let Codex operate there directly.

The feature I am requesting is official full Computer Use support for Codex Desktop on Windows, including:

• Screen inspection / screenshot understanding
• Mouse movement, clicking, double-clicking, dragging, scrolling
• Keyboard input and hotkeys
• Clipboard-aware workflows
• Operation of native Windows desktop applications
• Operation across normal developer tools such as VS Code, Cursor, terminals, browsers, file explorer, installers, configuration panels, and GUI-only tools
• Compatibility with Windows + WSL2 development workflows
• Clear user permission prompts and approval gates for sensitive actions

Why this matters:

Windows is a first-class development platform for many users. A large number of engineers use Windows together with WSL2, VS Code / Cursor, browsers, local GUI tools, remote Linux servers, and internal enterprise applications. Browser Use is valuable, but it only solves browser-contained workflows. It does not solve real desktop automation.

Without Windows Computer Use, Windows-first users need to buy or maintain a Mac only for this one capability. That is a significant barrier, especially when their main work environment, files, terminals, VPNs, enterprise tools, and developer setup already live on Windows.

Expected behavior:

Codex Desktop on Windows should expose a full Computer Use capability, ideally similar to the macOS implementation. Users should be able to explicitly enable it, grant the required permissions, and then let Codex inspect and operate the Windows desktop under user supervision.

Safety expectations:

I would be completely fine with this being opt-in and permission-gated. For example:

• Per-session approval before enabling screen control
• Visible indication when Codex is observing or controlling the desktop
• Confirmation before destructive, financial, security-sensitive, or credential-related actions
• Ability to pause or revoke control immediately
• Activity logs for actions performed by Codex

This would make Codex much more useful for Windows-first developers and engineering users. It would also remove the need to switch to macOS only to use Computer Use.

Additional information

Windows is my primary workstation, and I believe this is true for many developers.

Codex on Windows already feels close to being a complete engineering assistant: it can work with projects, Git, terminals, WSL2, browser workflows, and development files. The missing piece is the ability to operate the real Windows desktop environment.

Full Windows Computer Use would make Codex useful for end-to-end workflows that combine code and GUI operations, such as testing desktop apps, configuring tools, operating dashboards, reproducing UI bugs, using Windows-only software, and coordinating browser + terminal + desktop workflows.

This is not just a convenience feature. It determines whether Windows users can use Codex as their main AI agent on their main machine, or whether they need to buy and maintain a separate Mac only to access Computer Use.

I personally tried using a Mac mini for this workflow, but switching platforms introduced too much friction for my daily setup: keyboard behavior, mouse behavior, copy/paste habits, window management, monitor setup, and general usage habits. I would strongly prefer to use Codex Computer Use on my existing Windows workstation.