Codex Now Supports Remote Control on Windows: Your Phone Becomes a Console for a Windows Dev Machine¶

For / Key Points

For: Developers and team leads who use Codex for long-running coding, testing, or desktop tasks.

Key Points:

Codex app v26.527 lets ChatGPT on iOS or Android, or Codex on Mac, control a Windows host
The phone sends prompts, approvals, and follow-ups while execution stays on the Windows machine
Windows Computer Use runs in the foreground, so remote supervision is especially useful

On May 29, 2026, OpenAI added Computer Use and remote control support for Windows in Codex app v26.527.¹ OpenAI had introduced Codex in the ChatGPT mobile app on May 14, but Windows host support was still listed as coming soon at that time.⁴ That missing piece is now in place.

This article answers one question: can a Windows PC act as the Codex execution host while a person safely supervises from a phone?

The practical answer is yes for long-running implementation, testing, and screen-checking workflows. There is one important constraint: Computer Use on Windows runs in the foreground. That constraint should shape how the workflow is designed.

What Changed¶

The v26.527 update matters to Windows users in three ways.

Computer Use now works on Windows: Codex can see, click, and type in Windows desktop apps while it works.¹
Remote Control now supports Windows hosts: ChatGPT on iOS or Android, and Codex on Mac, can start work on a Windows device and check progress remotely.¹
The Profile section is richer: It now shows profile details, usage stats, and token activity.¹

The second point is the bigger operational change. Once a phone can see and steer Codex threads running on a Windows machine, execution and supervision can happen in different places. A desk PC, home workstation, or always-on Windows box can do the work while the person approves, redirects, or reviews from mobile.

This is not just a notification feature. It makes the live Codex work surface reachable from another authorized device.

What the Phone Actually Controls¶

Remote control does not move the development environment onto the phone. Repository files, local documents, credentials, plugins, MCP servers, shell commands, and Computer Use configuration all come from the connected host.² The phone acts as the command and review console.

OpenAI's remote connections documentation lists the core remote actions as follows.²

Start new threads in host projects, or continue existing threads
Send follow-up instructions, answer questions, and steer active work
Approve commands and other actions
Review outputs, diffs, test results, terminal output, and screenshots
Receive task-completion or attention-needed notifications, and switch between hosts and threads

That division of responsibility is the key. The phone is not a lightweight IDE. It is a remote console for preventing Codex from getting stuck at judgment points.

Initial Setup¶

Setup starts from the Codex app on the host. OpenAI's docs state that mobile setup cannot be initiated from the Codex CLI or IDE extension.²

Use the same account: Sign in to the Windows Codex app and the ChatGPT mobile app with the same ChatGPT account and workspace.
Update both apps: Use the latest ChatGPT mobile app on iOS or Android and the latest Codex app on the Windows host.
Pair with a QR code: Start mobile setup from the Codex app sidebar and scan the QR code with your phone.
Review connection settings: Use Settings > Connections in Codex to manage connected devices, wake behavior, Computer Use, and the Chrome extension.

The first test should be low risk. Ask Codex to summarize a README, check a test result, or review a small diff. Confirm that notifications, approvals, screenshots, and terminal output arrive as expected.

Choosing the right host matters. A normal Windows laptop works, but sleep or network loss stops remote access. For longer-running work, an always-on Windows PC or managed SSH environment is usually a better host candidate.²

Why Computer Use Makes Remote Control More Valuable¶

The interesting part of this release is that remote control and Computer Use arrived together for Windows.

Computer Use lets Codex operate desktop apps by seeing the screen and using the mouse and keyboard.³ It is useful for UI testing, logged-in application checks, screen-only bug reproduction, and visual review of PDFs or slides. Code editing and test execution can remain in the shell, while screen-specific work goes through Computer Use.

On Windows, however, Computer Use runs on the active desktop. It cannot operate in the background while the person keeps using the same Windows session.³ Codex will move the pointer, type, and take over the foreground while the task runs.

That is exactly where remote control helps. The Windows machine can be dedicated to Codex execution, while the person monitors progress and approves actions from a phone. The foreground limitation becomes easier to accept when the machine is treated as an execution host rather than a shared interactive desktop.

Good Uses and Bad Uses¶

Remote control should not move every approval onto a phone. It works best when the mobile interaction is short, reviewable, and reversible.

Situation	Why it fits	Watch out for
Long tests or builds	You can receive completion notifications and send the next instruction	Long failure logs may still need a full desktop
Small implementation reviews	Diffs, explanations, and test results are reviewable on mobile	Large refactors are hard to inspect on a small screen
GUI bug reproduction	Computer Use screenshots expose the current screen state	The Windows host desktop is occupied
Direction changes	Active work can keep moving without waiting for you to return	Vague mobile instructions can create rework

The risky cases are billing, administrator privileges, production environments, security settings, and destructive file operations. A phone screen makes it easier to miss context or skim a diff too quickly. Sandboxing, security controls, and action approvals still apply to connected remote sessions, but the quality of the final judgment depends on the human review environment.²

A Safe Starting Pattern¶

Start with one host, one project, and narrow permissions.

Connect only trusted devices that you control
Check lock, sleep, and network behavior on the Windows host
If Computer Use is enabled, do not leave sensitive windows or admin consoles open
Decide in advance which actions can be approved from mobile and which require returning to a desktop
Periodically review connected devices in Settings > Connections

The value is not that everything can be approved from a phone. The value is that short judgment points no longer stop long-running Codex work.

Summary¶

This update is larger than basic Windows desktop automation. It makes a Windows PC a practical Codex execution host that can be supervised from mobile.

That changes the operating model. The person no longer has to sit in front of the PC while Codex works. The PC continues the task, and the person returns only the necessary decisions. Windows Computer Use's foreground behavior also becomes easier to design around when this division is explicit.

Start with a small repository, short task, and low-risk approval. Once notifications, diffs, test output, and screenshots flow reliably, the operating model changes. The Windows machine starts to feel less like a workstation you must sit at and more like an execution host you can steer.

OpenAI, Codex changelog - Computer use and mobile access on Windows, 2026-05-29. ↩↩↩↩
OpenAI, Remote connections - Codex. ↩↩↩↩↩
OpenAI, Computer Use - Codex app. ↩↩
OpenAI, Work with Codex from anywhere, 2026-05-14. ↩