GitHub
@github
Start work on your computer, continue your local session anywhere. 📲 Remote control for GitHub Copilot CLI and @code sessions is now generally available. https://t.co/wwSEBd5lqL https://t.co/Yc5R6tBfBl
41retweets307likes
View on XGitHub Launches Remote Control for Copilot CLI to Steer Agents Anywhere
GitHub launched Remote Control for GitHub Copilot CLI and
@code sessions in general availability. This feature bridges a local terminal with the GitHub web or mobile interface, allowing you to monitor progress and provide human-in-the-loop (HITL) feedback from any device.- Availability
- General Availability
- Remote interfaces
- GitHub.com and GitHub Mobile
- Enterprise policy
- Disabled by default
- Execution location
- Local machine
- Session requirement
- Interactive only
As coding agents move toward GitHub Copilot's parallel execution, tasks often take significant time. Previously, developers were tethered to their desks to approve file edits. This update mirrors Claude Code's session mobility, turning the terminal into a persistent, mobile-accessible state rather than a static local process.
You can now start a session locally and step away, using GitHub Mobile to approve permissions, answer questions, or submit prompts. The feature is available to all Copilot users, though enterprise owners must manually enable the Remote Control policy. All operations continue to execute securely on your local machine.
Still wondering? A few quick answers below.
Remote control is a feature that allows you to monitor and steer an active GitHub Copilot CLI session from GitHub.com or the GitHub Mobile app. While the AI agent continues to run on your local machine, you can respond to prompts, approve file permissions, and submit new instructions from another device even after stepping away from your workstation.
When you enable remote control, your local session events are streamed to GitHub in real time. You can then access the session through a specific URL on the web or mobile app. Both the local terminal and the remote interface remain active simultaneously, and the CLI uses the first response it receives from either interface to proceed with its work.
Remote control is now generally available to all GitHub Copilot users. However, if your access is provided through an organization or enterprise, an administrator must first enable the Remote Control policy, which is turned off by default. Once enabled, only the authenticated user who started the local session can access and interact with it remotely for security.
No, the machine where the session was started must remain online and the CLI session must be actively running in a terminal. If the machine loses its internet connection or goes to sleep, remote control becomes unavailable. You can use the keep-alive command within the CLI to prevent your local machine from entering sleep mode during long-running tasks.
GitHub Copilot coding agents run entirely in the cloud on GitHub's infrastructure and operate asynchronously. Remote control is designed for local CLI sessions that you initiate and manage yourself. The remote control feature allows you to interact with your own running session from another device, whereas cloud-based agents work autonomously without a local terminal.
