Turn ChatGPT into a Remote AI Operator: Control Codex Desktop & Your Computer from Anywhere

ChatGPT Feature requests
,
1

Turn ChatGPT into a Remote AI Operator: Control Codex Desktop & Your Computer from Anywhere

Hi everyone,

I’d like to propose a feature that could take ChatGPT and Codex to the next level: enabling users to remotely control a desktop environment (local or virtual) directly from the ChatGPT mobile app.

The core idea is to go beyond code assistance and allow Codex to act as a true AI operator capable of executing real tasks on a computer. This would include:

  1. Remote Control of Codex Desktop
    From a mobile device, users could interact with their Codex Desktop environment—sending instructions, reviewing outputs, and supervising actions in real time.

  2. Action-Oriented Capabilities (Beyond Code)
    Instead of limiting interactions to programming, users could request tasks such as:

  • Generating PowerPoint presentations
  • Managing emails
  • Organizing files
  • Running software workflows
  • Automating repetitive desktop actions

This would essentially bring an experience similar to an AI-powered operating assistant, capable of handling a wide range of real-world tasks.

  1. Virtual Computer Environment (Optional but Powerful)
    In addition to controlling a local machine, OpenAI could provide a hosted virtual desktop environment directly accessible through ChatGPT.
    This environment could function like a secure, sandboxed virtual machine where Codex executes tasks on behalf of the user.

  2. Seamless Integration into Existing Plans
    Rather than introducing a completely separate product, this capability could be integrated into current subscription tiers, potentially as a feature. This would make it accessible while still aligning with existing offerings.

The goal is to create a unified experience where ChatGPT becomes not just a conversational assistant, but an actionable interface to your digital environment—whether local or cloud-based.

This kind of system could dramatically improve productivity by allowing users to delegate complex workflows and interact with their computer from anywhere.

Curious to hear what others think about this direction!

Thanks.

Sam (Aka Alexandre)

2

I’d like to add a quick real-world observation specifically related to Codex on Windows.

Recently, one of my clients started using ChatGPT codex desktop as a kind of operational assistant for SEO work. Instead of just generating ideas, they actually use it to produce DOC files, write structured content, draft emails, and help manage day-to-day tasks around content production.

What’s interesting is that this kind of usage doesn’t really fit into the current vision of Codex Desktop on Windows, which is still mainly focused on coding workflows and agent-based development. Yet in practice, users are already pushing these tools beyond code into broader productivity use cases.

It feels like there’s an opportunity here to evolve Codex on Windows into something more versatilecloser to a general-purpose assistant that can actively create documents, handle communication, and support real workflows, not just development tasks. It can be great also to make Codex compatible to OpenClaw Skill but in a more secure way but stay connected to this open source ecosystem

Curious if others are seeing similar patterns.

3

I would also like to add my thoughts on this topic. This idea seems aligned with the direction software development is going:

Feature Proposal: Unified ChatGPT and Codex Cross-Device Workflow

I would like to propose a more unified workflow between the ChatGPT and Codex apps, particularly across Windows or Mac desktop and mobile.

Summary

Please consider bringing ChatGPT and Codex closer together so that users can begin technical work on a Mac or Windows PC and continue meaningfully from a mobile phone while away from their desk.

The key idea is not only conversation sync, but workflow continuity. At present, normal ChatGPT conversations can be continued across devices, but local Codex work tied to files on a PC feels more isolated. A more connected experience would be extremely valuable for developers and technical users.

Main Use Case

I may begin work in Codex on my Mac or Windows PC against a local project or repository. Later, when I am away from the computer, I would like to open the ChatGPT app on my phone and continue in the same thread with awareness of:

  • the task already being worked on

  • the recent commands and outputs

  • the files that were being discussed or changed

  • the current state of the work

  • what remains to be reviewed, approved, or run next

Even if my phone cannot directly access the PC filesystem, I would still like the mobile app to function as a continuation point for the same job.

Example Scenario

  • I start a task in Codex on Windows to modify code in a local repository.

  • Codex inspects files, proposes changes, runs commands, and produces diffs.

  • I leave my desk.

  • On mobile, I open the same thread in ChatGPT and can:

    • review progress

    • read summaries of changes made

    • inspect diffs or proposed next steps

    • ask follow-up questions

    • approve or reject actions

    • leave instructions for when I return to the Mac or my Windows PC

This would make ChatGPT and Codex feel like parts of one development environment rather than separate surfaces.

Requested Capabilities

1. Unified conversation and task continuity

A Codex task started on desktop should appear as a first-class conversation or project thread in ChatGPT mobile.

2. Persistent execution context summary

When a local Codex task is in progress, the mobile app should show:

  • current objective

  • recent actions taken

  • pending actions

  • changed files

  • diffs awaiting approval

  • blockers or failed commands

3. Remote review mode

From mobile, I should be able to:

  • read the latest state of the task

  • comment on proposed changes

  • approve or reject diffs

  • ask for another approach

  • queue follow-up instructions

4. Desktop relay or handoff mode

If direct remote execution is not appropriate, the Windows Codex app could remain the execution host while mobile acts as a control and review layer.

5. Clear distinction between local and cloud context

The interface should make it obvious when work is:

  • local to a specific machine

  • running in a cloud environment

  • available for review only

  • waiting for the desktop to come back online

Why This Matters

This would solve a real workflow gap for developers and technical users.

Benefits include:

  • better continuity between desk work and remote review

  • reduced friction when stepping away from a machine

  • easier supervision of longer-running technical tasks

  • stronger integration between OpenAI’s desktop and mobile experiences

  • a more coherent product story around ChatGPT and Codex

Product Value

A unified experience would make the ecosystem feel significantly more polished and powerful.

Right now, ChatGPT is excellent for conversation continuity, while Codex is powerful for hands-on technical work. Combining those strengths more tightly would create a much stronger developer workflow, especially for users who move between desktop and mobile throughout the day.

The result would be quicker task completion and, in turn, faster project delivery overall, which appears to align with the broader direction of the platform.

Suggested Implementation Approaches

Any of these would be useful:

  1. Unified thread model
    Codex sessions appear directly inside ChatGPT conversations/projects.

  2. Remote review companion
    Mobile can review and guide local Codex work without requiring direct filesystem access.

  3. Desktop-hosted execution with mobile control
    The PC remains the executor; mobile acts as a secure review and approval interface.

  4. Cloud-synced task state
    Even when files are local, task metadata, summaries, diffs, and decisions sync across devices.

Final Request

Please consider a roadmap direction where ChatGPT and Codex feel like one connected system across Windows/Mac and mobile, especially for local development workflows.

For users doing real technical work, the ability to start on desktop and continue from mobile would be a major improvement.

4

Thanks for adding more context