--- title: "OpenAI's Codex Brings Screen Control and Mobile Steering to Windows" subtitle: "Codex can now drive Windows desktop apps directly and accept commands from your phone, closing the gap with the macOS version released earlier this year." url: "https://alphasignal.ai/news/openai-s-codex-brings-screen-control-and-mobile-steering-to-windows" author: "AlphaSignal Newsroom" author_url: "https://alphasignal.ai/editorial-team" company: "OpenAI" company_url: "https://alphasignal.ai/company/openai" published: "2026-05-29T18:30:34.000Z" updated: "2026-06-04T23:18:05.564Z" type: "News" topics: - "Agents" - "Development" subtopics: - "Computer Use" - "Code Agents" - "Code Agents" upvotes: 8788 read_time: "4 min" source_url: "https://x.com/openai/status/2060428604727771421" comments: 0 --- # OpenAI's Codex Brings Screen Control and Mobile Steering to Windows > Codex can now drive Windows desktop apps directly and accept commands from your phone, closing the gap with the macOS version released earlier this year. Mac users got the fun first. Now Windows catches up. The Codex desktop app has gained [computer use](https://developers.openai.com/codex/app/computer-use) on Windows, which means OpenAI's coding agent can see your screen, click buttons, and type into applications the way you would. Pair that with new mobile control through the ChatGPT app, and the developer workstation starts looking less like a tool you operate and more like an endpoint your agent operates for you. [Available through the Microsoft Store](https://www.neowin.net/news/openai-rolls-out-major-codex-for-windows-update-with-computer-use-and-mobile-access/) as Codex app version 26.527, the update brings two capabilities that had been Mac-only: GUI automation and remote steering from a phone. More than 4 million people now use Codex every week, and a sizable chunk of them have been stuck watching macOS get every interesting feature first. ## What computer use actually does Codex can operate Windows desktop apps by reading the screen, clicking interface elements, and typing through a task flow. It can use that capability to test interfaces, step through bugs, and review work where the project context already lives on the machine. The point is to handle the messy parts of software work that do not fit neatly into a repo or an API call. Triggering it is simple. Users can mention @Computer or an @AppName in the prompt after installing the Computer Use plugin in settings. From there you describe the app, window, or flow you want Codex to drive, and it takes over from there. Good fits, per the [official docs](https://developers.openai.com/codex/app/computer-use): - Testing a macOS app, Windows app, iOS simulator flow, or another desktop app that Codex is building - Reproducing a bug that only appears in a graphical interface - Changing app settings that require clicking through a UI - Inspecting information in an app or data source that isn't available through a plugin ## The Windows catch nobody warned you about Here is the big asterisk. 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 does not get that. On Windows, computer use runs on the active desktop. It can't operate in the background while you keep using the same Windows session, so expect Codex to move the pointer, type, and take over the foreground while the task runs. If you want to keep working, the documented workarounds are to leave the machine unlocked and steer from your phone, or run Codex inside a Windows VM so the agent takes over the VM instead of your main desktop. A few other limits worth knowing: The feature can't automate terminal apps or Codex itself, since automating them could bypass Codex security policies. It also can't authenticate as an administrator or approve security and privacy permission prompts on your computer. And computer use is available on macOS and Windows, except in the European Economic Area, the United Kingdom, and Switzerland at launch. ## Your phone becomes the dashboard The mobile piece is what makes the foreground constraint workable. When you connect to any of your machines where Codex is running, the app loads the live state from that environment so you can work fluidly across active threads, approvals, plugins, and project context. From the phone you can start new threads, send follow-ups, approve actions, review diffs, change models, and check screenshots or terminal output. Because the work happens on the Windows (or Mac) host, the phone becomes a review surface rather than a remote execution environment. Approvals and screenshots stay in front of the user while Codex performs the task on the PC. For a developer away from the desk, that means a build or UI check can continue without losing the approval point. ## Privacy and the trust boundary Computer use processes whatever is on your screen through OpenAI's servers. If sensitive credentials, customer data, or proprietary UI mockups happen to be visible, they get uploaded. If Codex uses your browser, it can interact with pages where you're already signed in. Review website actions as if you were taking them yourself: web pages can contain malicious or misleading content, and sites may treat approved clicks, form submissions, and signed-in actions as coming from your account. That shift, from suggesting code to executing on behalf of a logged-in user, is the real change here. [As one analysis put it](https://windowsforum.com/threads/codex-on-windows-11-control-computer-use-from-chatgpt-mobile.420839/), the main risk is not bad autocomplete, but delegated action on a real machine with real files, tools, permissions, and possibly secrets. For scoped tasks like UI regression checks or reproducing a customer's bug report, that tradeoff is probably worth it. For anything touching production credentials, run it in a VM. ## Sources - [X post by @openai](https://x.com/openai/status/2060428604727771421) - [Computer Use - Codex app | OpenAI Developers](https://developers.openai.com/codex/app/computer-use) - [OpenAI rolls out major Codex for Windows update with computer use and mobile access](https://www.neowin.net/news/openai-rolls-out-major-codex-for-windows-update-with-computer-use-and-mobile-access/) - [OpenAI Codex Computer Use Now on Windows: Foreground Takeover, Europe Excluded](https://www.techtimes.com/articles/317531/20260601/openai-codex-computer-use-now-windows-foreground-takeover-europe-excluded.htm) - [Work with Codex from anywhere | OpenAI](https://openai.com/index/work-with-codex-from-anywhere/) - [Codex on Windows 11: Control Computer Use from ChatGPT Mobile](https://windowsforum.com/threads/codex-on-windows-11-control-computer-use-from-chatgpt-mobile.420839/)