OpenAI rolled out Computer Use for Windows in Codex version 26.527 on May 29, 2026 — a long-requested update that lets the agent see, click, and type through graphical Windows applications the way a human user would. Windows developers can now point Codex at a native app, a browser flow, or a settings panel and let the agent complete the task visually — without needing a structured plugin or API integration. But there is a non-negotiable constraint that Windows users need to understand before they enable it: Codex runs in the foreground on Windows, meaning it takes over the active desktop session for the duration of the task. If you plan to keep working on the same machine while Codex operates, you cannot — and for users in the European Economic Area, the United Kingdom, or Switzerland, the feature is unavailable at launch entirely.
Windows Gets Computer Use, but Occupies Your Desktop
The foreground-only model is the central thing to understand about Codex Computer Use on Windows, and it is the most important way the Windows implementation differs from the Mac version. On macOS, Codex introduced background computer use in April 2026 as part of what OpenAI called "Codex for (almost) everything" — a design that lets multiple agents work on Mac applications in parallel, with their own cursors, without interrupting anything the user is doing in the foreground. Windows has no equivalent background-session capability at this time.
On Windows, according to OpenAI's developer documentation, Computer Use runs on the active desktop. The agent will move the pointer, type into applications, and take over foreground input while the task runs. For tasks that need to continue while a developer steps away, OpenAI recommends keeping the Windows machine unlocked and connected to the internet — and steering the task remotely from a phone. Running Codex inside a Windows virtual machine is the other documented option for users who want to isolate the agent to its own session rather than surrendering the main desktop.
The practical implication for Windows users is significant. Deliberate runs — reproducing a GUI bug in a native app, clicking through an installer, testing a checkout flow in a browser, or verifying that a settings panel behaves correctly after a code change — fit this foreground model well. The machine becomes a dedicated workbench for the duration of the task. What does not fit: running Codex as a background worker on a Windows machine where a developer expects to keep using other applications simultaneously. That use case remains Mac-only for now.
ChatGPT Mobile App Now Connects to Windows Hosts
The May 29 release paired Computer Use with Windows support in the ChatGPT mobile app for Codex, giving the two capabilities a practical relationship. A developer can now start a Codex task on a Windows machine — or leave one running — and check in from an iPhone or Android device using ChatGPT. The phone sends prompts, approvals, and follow-up instructions; the Windows machine supplies the project files, shell access, plugins, Model Context Protocol (MCP) servers, browser access, and the active desktop environment for Computer Use.
What this enables in practice: a developer can kick off a multi-step GUI task on a Windows desktop, leave the machine running with Computer Use active, and then monitor progress, approve pending actions, or redirect the agent from anywhere. The Windows PC remains the operating surface; the phone is the remote control. OpenAI's documentation specifies that the Windows host must remain unlocked and internet-connected for this remote workflow to function — a requirement that developers managing unattended overnight tasks should plan for specifically.
What Codex Computer Use Can Do on Windows
The capability set for Windows matches the Mac implementation in most respects, per OpenAI's Computer Use documentation. Codex can operate any Windows desktop application the user can see — native apps, settings panels, browsers, and data sources that do not expose a structured plugin — by reading the screen, clicking interface elements, and typing through task flows. The feature is activated by installing the Computer Use plugin from Codex settings, and each application requires explicit permission before Codex can operate it.
OpenAI specifically describes Computer Use as appropriate when a task depends on a graphical interface that is hard to verify through files or command output alone: reproducing a bug that only appears after clicking through an installer, testing an onboarding screen, verifying a checkout flow in a live browser session, or inspecting information in an app that has no API. Mentioning @Computer or a specific app name in a Codex prompt — for example, @Chrome — triggers the feature for that application.
How Does Codex Computer Use Protect User Data on Windows?
The permission model carries real implications. Computer Use can access screen content, take screenshots, interact with open windows, use menus, type into applications, and access clipboard state. OpenAI's safety documentation warns that this means the agent may encounter private browser pages, open files, signed-in services, and credentials visible on screen during a task. OpenAI's guidance tells users to keep tasks scoped, stay present for sensitive flows involving account credentials or payment information, and review permission prompts before allowing Codex to proceed.
A concern about the broader Computer Use feature — documented in the Codex GitHub repository on May 25, 2026 — involved the ambient suggestions feature on the macOS Codex desktop app triggering Computer Use to open Gmail in Chrome without a visible user-initiated task. The reported risks included email content entering model context, Codex having access to other signed-in sessions in the same browser, and the absence of a clear audit trail for the background action. OpenAI had not issued a public response to that specific issue as of the date of this article.
The broader security context is important here. Security researchers at BeyondTrust's Phantom Labs documented in December 2025 that Codex previously passed GitHub branch names into shell commands without sanitization — a flaw researcher Tyler Jespersen found could expose a user's GitHub authentication token. OpenAI patched the vulnerability on February 5, 2026. Check Point Research's Eli Smadja noted in March 2026: "Don't assume AI tools are secure by default."
Europe, UK, and Switzerland Cannot Use Codex Computer Use at Launch
Computer Use is not available in the European Economic Area, the United Kingdom, or Switzerland at launch — a restriction that applies equally to the Windows and Mac implementations, per OpenAI's documentation. OpenAI has not publicly explained the reason for the exclusion or provided a timeline for when availability in these regions might change. The Chronicle screen-memory feature, introduced for Mac in April 2026, carries the same geographic restriction — a pattern that suggests ongoing regulatory work with European data-protection authorities rather than a technical limitation.
Windows developers in affected regions can use the rest of the Codex Windows feature set — parallel agent threads, worktrees, plugins, Skills, the in-app browser, and Git workflows — but the graphical desktop-automation capability is unavailable to them.
Frequently Asked Questions
How is Codex Computer Use on Windows different from Mac?
On Mac, Codex uses background computer use — multiple agents can operate Mac applications in parallel with their own cursors while the user continues working in the foreground, uninterrupted. On Windows, computer use runs in the foreground only: Codex takes over the active desktop session, moving the pointer and typing into applications while the task runs. The user cannot continue working in the same Windows session while Codex operates.
Can Codex run in the background on Windows?
No. As of version 26.527, Codex Computer Use on Windows is foreground-only and cannot operate silently while the user keeps the same Windows session active. For tasks that need to run unattended, OpenAI recommends keeping the Windows device unlocked and connected, then steering and monitoring the task via the ChatGPT mobile app on iOS or Android.
Is Codex Computer Use available in Europe?
Computer Use is not available in the European Economic Area, the United Kingdom, or Switzerland at launch. This restriction applies to both the Windows and Mac implementations. OpenAI has not publicly provided a timeline for when the feature will be available in those regions.
What permissions does Codex Computer Use require on Windows?
Users must install the Computer Use plugin from Codex settings and grant per-application permissions before Codex can operate any desktop app. Codex requests access for each application individually, and users can choose whether to allow automatic access in future tasks. OpenAI advises staying present during tasks that touch account credentials, payment information, or other sensitive settings.
ⓒ 2026 TECHTIMES.com All rights reserved. Do not reproduce without permission.
