Feature request: Windows-to-Windows Codex Remote Control
What variant of Codex are you using?
App
What feature would you like to see?
Please enable the Codex app on a Windows laptop to remotely connect to and control a Codex host running on another Windows computer.
Codex Remote already allows access to a Windows host from iOS/iPadOS and macOS. Extending this capability to the Windows desktop app would let users continue working from a laptop while away from their primary desktop, preserving the same projects, local context, tools, plugins, terminals, and active tasks.
This would create a unified Codex work environment across Windows devices, reduce duplicated setup and repository synchronization, and improve productivity for users who alternate between desktop and laptop computers. The existing authenticated, one-to-one pairing model could provide the same security controls.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
+1 to this!
I'd like to add another use case that I think broadens this request.
My primary windows workstation stays powered on and serves as a permanent AI host. It runs Codex, Docker Desktop, local LLMs, MCP servers, SSH connections, long-running agent tasks, repository context, project skills, and DESIGN.md files.
When I'm elsewhere in the house or traveling, I usually carry only a MacBook Air because it's lightweight and has excellent battery life.
I already have Sunshine/Moonlight and other Remote Desktop solutions if I need to control Windows itself.
What I'm hoping for is not Remote Desktop, but another authenticated ChatGPT desktop client that can attach to an existing Codex host session in the same way my IOS mobile app currently does.
For me, the ideal model would be:
Essentially, I'd love to see Codex evolve into a host/client architecture where the powerful workstation remains the compute host and any authenticated ChatGPT client becomes a first-class interface to that running environment.
It's essentially exactly what is already implemented in the IOS app just expanded.
+1 for this request. I want to use one Windows Codex Desktop app as a client for another Windows PC running Codex as the host. The existing SSH/Hermes setup provides separate CLI/backend access, but it does not attach to the host’s live Codex desktop session. The desired behavior is authenticated Windows-to-Windows pairing with the host’s existing projects, threads, local tools, plugins, terminals, approvals, and active tasks preserved—similar to the current mobile/Mac-to-Windows remote-control model.