Support first-class Windows-to-Windows Codex App pairing and remote control

What variant of Codex are you using?

Codex App on Windows / Windows-to-Windows usage

What feature would you like to see?

Please add first-class support for connecting two Codex desktop apps on Windows, so one Windows machine can act as the Codex host and another Windows machine can control it through the official Codex App experience.

Desired behavior:

• Pair two Windows Codex Apps through a supported flow, for example QR code, device code, or signed account-based pairing.
• Let the control machine browse the host machine's projects, threads, plans, command output, diffs, approvals, and file changes.
• Keep the host machine as the only real execution environment: files, credentials, plugins, .codex state, git worktrees, and tool execution stay on the host.
• Do not require users to copy .codex, auth files, SQLite/WAL state, or tokens between machines.
• Avoid requiring users to manually build a custom web gateway around codex app-server.
• Support Windows-native environments, including cases where RDP/SSH setup is unavailable, unreliable, or too much overhead.
• Include reliable reconnect, host naming, stale host cleanup, and clear status/error messages.
• Provide a safe transport model: private relay, account-mediated pairing, or documented VPN/mesh-network mode, without exposing codex app-server directly to LAN/public networks.

Additional information

The current workaround is operationally heavy. In my case, I had to build a custom Windows remote console project:

• A Node gateway runs on the real Codex host.
• The gateway launches codex app-server over stdio.
• A browser on the second machine talks to that gateway.
• Tailscale Serve is used for cross-machine access.
• Extra care is required not to expose .codex/auth.json, SQLite/WAL files, tokens, or app-server internals.

This works as a workaround, but it is too much infrastructure for a normal user who simply wants to use one Windows Codex environment from another Windows computer.

There are already many Windows remote/app-server issues, but this request is specifically for a polished first-party Windows-to-Windows Codex App connection flow rather than asking users to assemble their own app-server gateway, RDP fallback, SSH setup, or Tailscale wrapper.