Take Your GitHub Copilot Workflows Anywhere with Remote Control

GitHub Copilot has transformed how developers leverage AI-assisted coding, but managing multiple agent sessions across different tools can be a juggling act. Until now, you could only oversee active sessions from your desktop. With the new remote control capabilities for GitHub Copilot CLI—now generally available on github.com and the GitHub Mobile app, plus expanded support in VS Code and JetBrains IDE—you can monitor, steer, and complete workflows from any device. Whether you're refactoring code, debugging tests, or scaffolding new features, remote control lets you take your sessions on the go without losing visibility or control.

What is remote control for GitHub Copilot?

Remote control is a feature that lets you manage your GitHub Copilot sessions from any supported surface—like the web, mobile app, VS Code, or JetBrains IDE. Instead of being tied to a single machine or terminal, you can start a session in the CLI or VS Code, then use the /remote on command to transfer it to another device. This creates a continuous workflow across all your tools. For example, you could begin planning a feature with Copilot CLI at your desk, then monitor its progress on your phone while commuting. Remote control works with any repository and even non-repository directories, making it flexible for any setup.

How does remote control work?

To use remote control, start a Copilot session as you normally would in the CLI (with GitHub Copilot CLI) or in VS Code. Then simply type /remote on to send that session to the web or GitHub Mobile app. From there, you can view the session in real time, see what Copilot is doing, and send follow-up instructions. The session remains private to you, and no other user can access it. There's no additional installation required if you already have the latest version of GitHub Copilot CLI or VS Code extension. For CLI users, install Copilot CLI first. Once active, you can switch between devices seamlessly.

Can I monitor sessions in real time from another device?

Yes, you can open your session on any supported device and watch Copilot's actions as they happen. The real-time view shows the plans it's researching, files it's reading, changes it's making, and commands it's executing. This is especially useful when you're away from your main workstation but need to keep an eye on progress. For instance, if you kicked off a complex refactoring task on your desktop, you can monitor it from your phone while walking to a meeting. The live feed ensures you never miss an important step—even if you need to quickly approve a permission request or adjust course.

Can I change instructions while a session is running?

Absolutely. Remote control allows you to send additional instructions to a running session using natural language, no matter where you are. If the agent is heading in the wrong direction, you can send a follow-up message to redirect it. You can also expand the scope of a task mid-flight—for example, telling your agent to add error handling while it's in the middle of implementing a feature. Permission requests (like file write access) can also be approved or denied from the remote interface. This flexibility means you can steer your workflows dynamically without returning to your desk, making development truly mobile.

What complete workflows can I do remotely?

With remote control, you can execute an entire developer workflow from a remote device, such as your phone. For example, start by using Copilot CLI to plan and scaffold a feature. Then use /remote on to transfer the session to the GitHub Mobile app or web. From there, monitor progress, steer the session with follow-up instructions, review the implementation plan and proposed changes, and even create and review a pull request—all from your phone. Once the PR is approved, you can merge it and move on. This end-to-end capability removes the friction of switching surfaces, allowing you to be productive anywhere. For more detailed steps, see the getting started guide.

Is remote control private and secure?

Yes, privacy is built in by default. Your sessions are only visible to you—no one else can see or access them. Remote control maintains the same level of privacy as your local sessions. The feature operates within your GitHub account, and all communication is encrypted. There are no sharing or collaboration features that expose your session to others. This ensures that sensitive code, plans, and outputs remain confidential. You can work on public or private repositories with the same assurance. If you're using GitHub Copilot in an enterprise environment, standard security policies apply.

How do I get started with remote control?

To start using remote control, first install GitHub Copilot CLI (if you don't have it yet). Then, launch a session in the CLI or VS Code. Once your session is active, type /remote on to send it to github.com or the GitHub Mobile app. If you already have the latest version of Copilot CLI or VS Code extension, no new installation is needed—just use the command as part of your normal workflow. You can also manage sessions from the web or mobile app directly. For comprehensive instructions, refer to the official documentation. Remote control is more than a convenience; it's a step toward an end-to-end agentic platform that keeps you productive wherever you are.