Feature Request: Remote Companion for ChatGPT Desktop / Work
Summary
It would be extremely useful to have a Remote Companion capability for ChatGPT Desktop, allowing users to control an active ChatGPT Desktop / Work session from another device, especially from the ChatGPT mobile app or web interface.
The main use case is not traditional remote desktop screen sharing. The idea is to remotely interact with a ChatGPT session that already has access to a local project, local files, development tools, browser sessions, and other desktop resources.
Problem
ChatGPT Desktop and Work can become deeply integrated with a local development environment.
For example, a user may have ChatGPT working on:
-
a local software project;
-
source code and documentation;
-
local repositories;
-
terminals and development tools;
-
browser sessions;
-
local configuration files;
-
project-specific context accumulated during the session.
However, once the user leaves the computer, that local-capability session becomes effectively inaccessible.
The ChatGPT mobile app can continue the conversation in the cloud, but it cannot currently act as a remote control for the active Desktop/Work session that still has access to the local environment.
This creates unnecessary interruptions in long-running development and project-management workflows.
Proposed Feature
Allow a ChatGPT Desktop / Work session to be exposed as a securely authorized Remote Session.
From the ChatGPT mobile app or web interface, the user could:
-
See active ChatGPT Desktop / Work sessions.
-
Select a machine and project.
-
Send additional instructions to the existing session.
Examples:
-
“Run the tests again.”
-
“Check why the build failed.”
-
“Update the architecture documentation with what we just discussed.”
-
“Review the changes you made.”
-
“Continue implementing the onboarding flow.”
-
“Commit the changes after verifying the tests.”
-
-
Receive questions from the Desktop agent and answer them remotely.
-
Follow execution progress and tool activity.
-
Receive the final result remotely.
-
Receive a notification when the Desktop session:
-
finishes a task;
-
encounters an error;
-
requires user input;
-
requires approval for a sensitive action.
-
Example Workflow
A developer is using ChatGPT Desktop Work on a local repository.
Before leaving the computer, the developer enables remote access for that Work session.
Later, from the ChatGPT mobile app, the developer sends:
“Please update the onboarding documentation with the decisions we just discussed and verify that the implementation matches the documentation.”
The command is routed to the ChatGPT Desktop session running on the user’s computer.
That Desktop session still has access to the local project and can inspect or modify the repository.
If the agent needs clarification, the question appears on the mobile device.
The developer answers from the phone.
The Desktop session continues execution and eventually sends the result back to the mobile app.
No traditional remote desktop connection or screen sharing is required.
Important Architectural Distinction
This feature should not simply be screen sharing or remote desktop.
The user should be remotely controlling the ChatGPT agent/session, not the computer UI itself.
Conceptually:
ChatGPT Mobile / Web
↓
Secure Remote Command Channel
↓
ChatGPT Desktop / Work Session
↓
Local tools / filesystem / browser / development environment
The actual execution remains on the user’s computer.
This architecture would preserve the major advantage of ChatGPT Desktop: access to local resources.
Security Model
The feature should be explicitly opt-in.
Possible controls:
-
Enable remote access per machine.
-
Enable remote access per Work session.
-
Allow only selected projects or directories.
-
Require device authentication or passkey confirmation.
-
Show all remotely initiated actions in the Desktop activity log.
-
Allow users to immediately revoke remote access.
-
Require explicit approval for sensitive operations.
-
Support configurable execution permissions.
For example:
Allowed automatically
-
Read files.
-
Run tests.
-
Analyze logs.
-
Update documentation.
-
Inspect source code.
Require confirmation
-
Delete files.
-
Push commits.
-
Deploy software.
-
Change production infrastructure.
-
Execute privileged system commands.
Additional Possibilities
This capability could eventually support:
-
multiple registered computers;
-
choosing which computer should execute a task;
-
remote notification when Work requires input;
-
continuing a Desktop session from another device;
-
remote approval prompts;
-
remote monitoring of long-running Codex/Work tasks;
-
mobile access to task progress;
-
scheduled tasks executed on a user’s workstation;
-
remote wake-up or reconnect mechanisms for authorized Work sessions.
Why This Would Be Valuable
For developers and other professionals, ChatGPT Desktop is becoming more than a chat application. It increasingly acts as an agent working directly with local projects and tools.
A Remote Companion would make that agent accessible without requiring the user to remain physically at the workstation.
It would turn ChatGPT Desktop into something closer to a persistent local AI worker that can be securely supervised and instructed from anywhere.
This could significantly improve workflows involving:
-
software development;
-
documentation;
-
DevOps;
-
data analysis;
-
research;
-
project management;
-
local automation.
A particularly useful implementation would be integration directly into the existing ChatGPT mobile app, where active Desktop/Work sessions could appear alongside normal conversations.
Possible names:
-
ChatGPT Remote Companion
-
Remote Work Sessions
-
Desktop Agent Remote Control
-
ChatGPT Work Companion
-
Remote Desktop Agent Sessions
My preference would be ChatGPT Remote Companion, since the feature is not really remote desktop — it is remote interaction with a locally running ChatGPT agent.