OpenAI Extends Codex to Control Windows Desktops via Mobile – AI Enters Real Workflows

OpenAI announced that Codex now supports Windows Computer Use, allowing the model to view and interact with the graphical desktop, and that the ChatGPT mobile app can remotely start, monitor, and approve tasks on a connected Windows machine.

This Update Adds Three Capabilities

First, the Codex App is officially available on both macOS and Windows, providing a desktop experience with worktree, automation, and Git integration.

Second, Computer Use on Windows lets Codex open applications, click buttons, change settings, and reproduce UI‑only bugs.

Third, the ChatGPT mobile app can control a connected Windows host, letting users launch new threads, continue existing ones, issue follow‑up commands, approve actions, view diffs, test results, and screenshots.

Why Windows Matters

While macOS covers many developer workflows, most enterprise tools, legacy client software, finance systems, and industry applications still run on Windows, often requiring GUI interaction that cannot be scripted via APIs alone.

Legacy systems with Windows‑only clients

Bugs that only appear in desktop applications

Form workflows that need an authenticated browser session

Settings hidden in multi‑level menus without CLI access

Tests that depend on visual UI changes

Previously AI could only advise on clicks; now Codex can actually move the mouse and type, effectively providing the missing “hand”.

Mobile Control as a Game‑Changer

The mobile app is not meant for coding on a small screen but for supervising long‑running AI tasks. Users can configure the environment on a PC, then use the phone to check where the task is stuck, approve commands, see test failures, verify diffs, or add brief instructions.

This turns the workflow from “person sits at the computer using AI” to “computer runs the task while the person oversees and dispatches via phone”.

Beyond IDE Plugins

AI coding tools have focused on IDE assistance—better completions, longer context, smarter PR reviews. Codex’s new direction is broader: it aims to be an execution layer that can control files, terminals, browsers, desktop apps, remote machines, and mobile devices.

Unlike typical IDE plugins that stay within code context, Codex App tries to control the entire environment where work happens, making GUI, login state, and system settings part of the context.

Safety and Practical Use

OpenAI warns that Windows Computer Use runs in the foreground, moving the mouse and typing in the active session, so it should be given a dedicated machine or VM. High‑risk actions (payments, account changes, sensitive settings) are discouraged.

Recommended safe scenarios include reproducing UI bugs, running a browser test of a changed page, checking a configuration in a Windows client, and performing small, interruptible tasks with the phone handling approvals.

The Underlying Signal

The announcement signals that OpenAI is moving Codex from a “code‑writing AI” toward an “AI that operates a computer to complete tasks”. The desktop handles the environment, the mobile app handles scheduling and supervision, and Computer Use bridges the gap between command‑line/API and GUI interaction.

When Codex can reliably act in the noisy, complex Windows desktop, its potential expands far beyond being a stronger code assistant to becoming a genuine remote work agent.

Reference Links

Codex App documentation: https://developers.openai.com/codex/app

Codex Remote Connections documentation: https://developers.openai.com/codex/remote-connections

Codex Computer Use documentation: https://developers.openai.com/codex/app/computer-use