Codex can now operate Windows PCs while users steer tasks from mobile

Why the Windows step matters

Codex is moving from a coding assistant that edits files toward an agent that can operate the machine where those files live. In its May 29 X post, OpenAI wrote, “Computer use now works on Windows”. That line matters because Windows remains a default development environment for many game, enterprise, .NET, embedded, and cross-platform teams.

The same post says Windows support also reaches Codex through the ChatGPT mobile app, so a user can start a task, review progress, and change direction while work continues on the PC. The tweet quickly crossed 950,000 views and more than 7,000 likes, which is strong evidence that the developer audience sees Windows support as a practical missing piece rather than a cosmetic update. OpenAI’s main account is used for first-party product and model rollouts, so this is a primary-source signal about Codex’s supported workflow.

What changes for developers

The important shift is execution context. A coding agent that can see, click, and type on Windows can test desktop apps, reproduce UI bugs, approve local flows, and inspect browser behavior without forcing the user to translate every action into text. That is especially relevant for long-running coding tasks where the agent needs to alternate between code changes and live validation.

OpenAI still frames the experience as early. The next checks are reliability, permission boundaries, latency from mobile control, and whether enterprise security teams accept remote agent access to developer machines. The source post is available on X.