GitHub Copilot Now Goes Wherever You Do: Remote Control for All Sessions Goes Live

Breaking: GitHub Launches Remote Control for Copilot Across All Devices

Starting today, developers can manage their GitHub Copilot agent sessions from any device, breaking free from the confines of a single laptop. The new feature, now generally available on github.com and the GitHub Mobile app, brings remote control to CLI, VS Code, and JetBrains IDE sessions.

This move effectively turns Copilot into a multi-surface, always-accessible tool. Developers can start a session on one device and pick it up on another without losing progress.

“This is about removing friction. Developers should be able to start a complex refactoring on their workstation and then monitor it from their phone while grabbing coffee,” said Sarah Chen, Senior Product Manager at GitHub.

How It Works

Using the /remote command, any active Copilot session in VS Code or the CLI becomes accessible on the web or the GitHub Mobile app. The session stays live, allowing real-time monitoring and control.

Remote control works with any repository, including directories without repos, so no setup changes are needed.

Real-Time Monitoring and Steering

From any device, you can see exactly what Copilot is doing — reading files, making changes, running commands, or researching plans. If the agent goes off track, you can send natural-language follow-up instructions to redirect it.

You can also approve or deny permission requests directly from your phone, ensuring you stay in control no matter where you are.

Complete Workflow from Anywhere

Remote control isn't just about seeing progress. You can complete entire workflows: plan and scaffold with Copilot CLI, monitor on mobile, steer with follow-ups, review implementation plans, and even create and merge pull requests — all from your phone.

“This transforms Copilot into a true agentic platform. Developers can now execute end-to-end tasks without being tied to a single screen,” added Chen.

Background

Until now, managing multiple Copilot agents — like one refactoring a module in VS Code, another debugging tests in the CLI, and a third scaffolding a feature — was only possible from a developer's desk. Stepping away meant losing visibility and control.

GitHub has been expanding Copilot's capabilities steadily, with CLI integration and agentic features rolling out over the past year. Remote control is the next logical step, making Copilot a companion that follows the developer, not the other way around.

What This Means

For developers, this eliminates the productivity gap when away from their primary machine. It enables more flexible workflows, reduces context switching, and allows collaboration on the go.

For teams, it means faster iteration cycles. A developer can approve code changes or steer an agent from a meeting, keeping projects moving without delays.

Remote control is private by default — sessions are visible only to the developer who started them. No one else can see or access your work.

Getting Started

Install GitHub Copilot CLI to begin. If you already have the latest version of the CLI or VS Code Copilot, there's nothing new to install. Simply start a session and use /remote to send it to the web or mobile app.

For detailed instructions, see the official documentation.