10 Things You Need to Know About Taking Your GitHub Copilot Sessions Anywhere

Imagine being able to oversee multiple GitHub Copilot agents working simultaneously—refactoring code, debugging tests, and scaffolding new features—without being chained to your desk. Now you can, thanks to remote control for GitHub Copilot CLI sessions, which is generally available on github.com and the GitHub Mobile app. New remote control capabilities in VS Code and JetBrains IDE make Copilot a truly multi-surface tool. This article breaks down ten key aspects of this feature, showing you how to manage your development workflows from any device.

1. Seamless Multi-Device Workflow

The core idea behind remote control is the ability to start a Copilot session in one environment—like the CLI or VS Code—and then continue it on another, such as github.com or the GitHub Mobile app. You might begin a complex planning session on your laptop, then step away and monitor progress from your phone. This cross-device continuity ensures that you never lose sight of your active agents, no matter where you go.

10 Things You Need to Know About Taking Your GitHub Copilot Sessions Anywhere — Source: github.blog

2. Real-Time Progress Tracking

Once a session is sent to the web or mobile, you can see exactly what Copilot is doing in real time. The live feed shows the plans being researched, files being read, changes being applied, and commands being executed. This level of visibility helps you catch issues early and stay informed about the status of each agent, whether you are in a meeting or commuting.

3. On-the-Fly Course Correction

If an agent starts heading in the wrong direction, you can send follow-up instructions in natural language to redirect it. For example, you might tell it to expand the scope of a task or refine its approach. This interactive control, available from any device, lets you steer the session dynamically without needing to restart or abandon your work.

4. Complete Workflow on Mobile

Remote control enables a full development cycle from your phone. You can scaffold a new project using Copilot CLI, then move it to the GitHub Mobile app to review the implementation plan, approve permission requests, and even create and merge a pull request—all without touching a desktop. This flexibility empowers developers to stay productive while away from their primary workstation.

5. Private by Default

Privacy is built into the remote control feature. Your sessions are visible only to you, and no one else can access or view them remotely. This ensures that your code, plans, and agent interactions remain confidential while you move between devices.

6. No Extra Installation Needed

If you already use the latest versions of GitHub Copilot CLI or GitHub Copilot in VS Code, you don’t need to install anything new. Simply start a session as you normally would and use the command /remote on to push it to the web or mobile. For new users, installing GitHub Copilot CLI is a quick first step.

7. Works with Any Repository or Directory

Remote control does not require a GitHub repository. You can work with any directory on your machine, even those without version control. This makes the feature versatile for projects that are not yet tied to a remote repository, expanding the scenarios where you can take your sessions on the go.

8. Available on GitHub.com and GitHub Mobile

After using /remote on, your session becomes accessible on github.com under your account and on the GitHub Mobile app. This dual support means you can check on progress using any modern web browser or smartphone, providing maximum flexibility for different contexts.

9. Remote Control in IDEs

Beyond the CLI, remote control is now integrated into VS Code and JetBrains IDE. This means you can send sessions from your IDE to web and mobile, giving you a seamless experience across the tools you use every day. It bridges the gap between local development and remote management.

10. Step Toward Agentic Development

This feature is more than a convenience—it is a step toward an end-to-end agentic platform. By enabling continuous, cross-surface workflows, GitHub Copilot is evolving into a tool that supports developers wherever they are. The ability to start, monitor, and steer sessions remotely lays the groundwork for a future where development is truly device-agnostic.

Remote control transforms how you interact with GitHub Copilot, freeing you from the confines of a single machine. Whether you need to monitor a session during lunch or complete a pull request from your phone, this capability ensures your development flow never stops. Try it today with /remote on and experience the power of agentic computing everywhere.