{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvsqt632xde6g4gn2rbo5gd524tkjrapir2krzij4bkiprw4j47u",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjlumwmcbiq2"
  },
  "path": "/t/turn-chatgpt-into-a-remote-ai-operator-control-codex-desktop-your-computer-from-anywhere/1378740#post_3",
  "publishedAt": "2026-04-16T07:02:11.000Z",
  "site": "https://community.openai.com",
  "textContent": "I would also like to add my thoughts on this topic. This idea seems aligned with the direction software development is going:\n\n**Feature Proposal: Unified ChatGPT and Codex Cross-Device Workflow**\n\nI would like to propose a more unified workflow between the ChatGPT and Codex apps, particularly across Windows or Mac desktop and mobile.\n\n**Summary**\n\nPlease 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.\n\nThe 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.\n\n**Main Use Case**\n\nI 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:\n\n  * the task already being worked on\n\n  * the recent commands and outputs\n\n  * the files that were being discussed or changed\n\n  * the current state of the work\n\n  * what remains to be reviewed, approved, or run next\n\n\n\n\nEven 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.\n\n**Example Scenario**\n\n  * I start a task in Codex on Windows to modify code in a local repository.\n\n  * Codex inspects files, proposes changes, runs commands, and produces diffs.\n\n  * I leave my desk.\n\n  * On mobile, I open the same thread in ChatGPT and can:\n\n    * review progress\n\n    * read summaries of changes made\n\n    * inspect diffs or proposed next steps\n\n    * ask follow-up questions\n\n    * approve or reject actions\n\n    * leave instructions for when I return to the Mac or my Windows PC\n\n\n\n\nThis would make ChatGPT and Codex feel like parts of one development environment rather than separate surfaces.\n\n**Requested Capabilities**\n\n**1. Unified conversation and task continuity**\n\nA Codex task started on desktop should appear as a first-class conversation or project thread in ChatGPT mobile.\n\n**2. Persistent execution context summary**\n\nWhen a local Codex task is in progress, the mobile app should show:\n\n  * current objective\n\n  * recent actions taken\n\n  * pending actions\n\n  * changed files\n\n  * diffs awaiting approval\n\n  * blockers or failed commands\n\n\n\n\n**3. Remote review mode**\n\nFrom mobile, I should be able to:\n\n  * read the latest state of the task\n\n  * comment on proposed changes\n\n  * approve or reject diffs\n\n  * ask for another approach\n\n  * queue follow-up instructions\n\n\n\n\n**4. Desktop relay or handoff mode**\n\nIf direct remote execution is not appropriate, the Windows Codex app could remain the execution host while mobile acts as a control and review layer.\n\n**5. Clear distinction between local and cloud context**\n\nThe interface should make it obvious when work is:\n\n  * local to a specific machine\n\n  * running in a cloud environment\n\n  * available for review only\n\n  * waiting for the desktop to come back online\n\n\n\n\n**Why This Matters**\n\nThis would solve a real workflow gap for developers and technical users.\n\nBenefits include:\n\n  * better continuity between desk work and remote review\n\n  * reduced friction when stepping away from a machine\n\n  * easier supervision of longer-running technical tasks\n\n  * stronger integration between OpenAI’s desktop and mobile experiences\n\n  * a more coherent product story around ChatGPT and Codex\n\n\n\n\n**Product Value**\n\nA unified experience would make the ecosystem feel significantly more polished and powerful.\n\nRight 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.\n\nThe result would be quicker task completion and, in turn, faster project delivery overall, which appears to align with the broader direction of the platform.\n\n**Suggested Implementation Approaches**\n\nAny of these would be useful:\n\n  1. **Unified thread model**\nCodex sessions appear directly inside ChatGPT conversations/projects.\n\n  2. **Remote review companion**\nMobile can review and guide local Codex work without requiring direct filesystem access.\n\n  3. **Desktop-hosted execution with mobile control**\nThe PC remains the executor; mobile acts as a secure review and approval interface.\n\n  4. **Cloud-synced task state**\nEven when files are local, task metadata, summaries, diffs, and decisions sync across devices.\n\n\n\n\n**Final Request**\n\nPlease consider a roadmap direction where ChatGPT and Codex feel like one connected system across Windows/Mac and mobile, especially for local development workflows.\n\nFor users doing real technical work, the ability to start on desktop and continue from mobile would be a major improvement.",
  "title": "Turn ChatGPT into a Remote AI Operator: Control Codex Desktop & Your Computer from Anywhere"
}