codex - 💡(How to fix) Fix Support mobile remote control for Codex App on Windows with SSH remote projects

Summary

Codex mobile remote control is now available through the ChatGPT mobile app, but the current public documentation says mobile setup currently requires the Codex App for macOS as the host, with Windows support coming soon. I use Codex App on Windows as my primary workstation and have SSH remote projects connected successfully there.

Problem

When SSH remote projects are already working in Codex App on Windows, those same working remote contexts do not appear to be controllable from the ChatGPT mobile app yet. This limits the usefulness of mobile Codex for users whose main development workstation is Windows and whose projects live on remote Linux servers.

Real-world use cases

1. Start or continue a Codex task from iPhone while away from the Windows machine.
2. Approve safe commands or diffs on a remote SSH project from mobile.
3. Monitor long-running diagnostics, tests, deploy checks, or migration tasks from mobile.
4. Keep working with remote Linux servers without needing physical access to the Windows workstation.
5. Use mobile as a control layer while the actual files, credentials, tools, and SSH setup remain on the Windows host.

Current workaround

The user must stay at the Windows machine to use connected SSH projects. Mobile Codex may be available generally, but it does not provide the same practical continuity for Windows-hosted SSH remote projects until Windows host pairing is supported.

Feature request

Add support for connecting the ChatGPT mobile app to Codex App on Windows, including access to SSH remote projects already configured and working inside the Windows Codex App.

Suggested design

• Allow Codex App on Windows to generate the same mobile pairing flow currently available for supported desktop hosts.
• After pairing, show the Windows host in Codex mobile.
• Preserve the same remote SSH project list and thread context available on the Windows Codex App.
• Let the user start, continue, approve, and review Codex work on SSH remote projects from mobile.
• Clearly display whether the active context is a local Windows project or an SSH remote project through the Windows host.
• Preserve all existing approval and permission boundaries.

Example contexts could be shown with generic labels such as:

• windows-workstation
• server-a:/app/service
• server-b:/app/worker

Security and UX safeguards

• Do not expose SSH credentials directly to the phone.
• Keep SSH keys, local config, tokens, and project files on the Windows host.
• Mobile should act only as a secure control and approval layer.
• Every command approval should clearly show the target context and, if applicable, the SSH remote host alias.
• If the Windows host is offline, asleep, or Codex App is closed, mobile should show a clear offline state.
• The UI should distinguish Windows host status from SSH remote project status.

Expected benefit

This would make Codex mobile useful for a large group of Windows users who manage Linux servers through SSH. It would also make the mobile rollout more complete for infrastructure, DevOps, server maintenance, migrations, and production/staging work.

Suggested labels, if available: enhancement, mobile, windows, ssh, remote-connections, feature-request

Redaction check

This report intentionally uses only generic examples. It does not include real hostnames, IP addresses, usernames, repository names, internal paths, company names, token references, or environment-specific identifiers.