GitHub Copilot Remote Control Now Generally Available for CLI and VS Code
Key Takeaways
- ▸GitHub Copilot remote control is now generally available for CLI and VS Code sessions, allowing developers to manage AI-assisted work from mobile devices or any web browser
- ▸The feature enables real-time management of long-running tasks, including permission approvals, answering prompts, and plan reviews, without requiring the user to be at the local machine
- ▸Remote control requires explicit policy enablement by organization administrators and depends on the local machine maintaining an active internet connection
Summary
GitHub has announced the general availability of remote control for GitHub Copilot CLI and VS Code sessions, enabling developers to manage their AI-assisted coding sessions from anywhere—including mobile devices via GitHub Mobile or from GitHub.com. The feature allows users to step away from their workstation while keeping the Copilot session running remotely, then monitor progress, respond to prompts, and continue work without returning to the original machine.
The remote control capability enables developers to handle time-sensitive interactions without being physically present. Users can approve permission requests for tools and file paths, answer questions when Copilot requires additional information, approve or reject plans in plan mode, submit new prompts, and switch between session modes. All actual CLI operations and file manipulations continue to run on the local machine, with the remote interface simply providing real-time monitoring and control.
To enable remote control, organization and enterprise administrators must first enable the "Remote Control" policy (off by default), and the machine running the Copilot CLI must remain online with an active internet connection. The feature is limited to interactive sessions and is not available when using the CLI programmatically with command-line options like --prompt, such as in scripts.
