Introduction

Developers often juggle multiple tasks simultaneously—refactoring code in VS Code, debugging tests in the CLI, or scaffolding new features in the background. GitHub Copilot makes this possible, but until now, managing all these sessions required staying tethered to your desk. The moment you stepped away from your laptop, you lost visibility into every running session.

With the new remote control feature for GitHub Copilot, you can take your sessions anywhere—on github.com, the GitHub Mobile app, and soon directly within VS Code and JetBrains IDE. This guide walks you through how to start a Copilot session, move it to another device, monitor progress in real time, and even change direction mid-flight—all from the palm of your hand.

What You Need

• GitHub Copilot subscription (individual, business, or enterprise)
• GitHub Copilot CLI installed (or the latest version of GitHub Copilot in VS Code)
• A GitHub account with access to the repository (or directory) you want to work in
• The GitHub Mobile app installed on your smartphone (optional for mobile control)
• A stable internet connection on both devices

No additional software is required if you already have the latest version of GitHub Copilot CLI or VS Code extension. The feature is enabled by default.

Step-by-Step Instructions

Step 1: Start a Copilot Session in Your Preferred Environment

Begin by launching a Copilot session in either the CLI or VS Code. For example, in the CLI use github-copilot-cli to start a planning session with /plan or a coding session with /explain. In VS Code, open the Copilot panel and initiate a new conversation. The session runs locally as it normally would—you’ll see it working on your primary device.

Step 2: Activate Remote Control with /remote on

Once your session is running, type the command /remote on in the chat or CLI. This command sends the session to the cloud, making it accessible from github.com and the GitHub Mobile app. You’ll receive a confirmation message with a direct link to the session on the web. The session remains private—only you can see or control it.

Step 3: Open the Session on Another Device

On your smartphone or another computer, open the link from the confirmation. Alternatively, navigate to github.com/copilot or tap the Copilot icon in the GitHub Mobile app. Your session will appear in the list of active remote sessions. Tap or click to open it. You’ll see the same interface as on your original device: the plan, files being read, changes being made, and commands being executed.

Step 4: Monitor Progress in Real Time

As Copilot works, you can watch its progress live. The remote view reflects exactly what the agent is doing—whether it’s researching a plan, reading files, writing code, or running commands. This transparency helps you stay informed without needing to be at your desk.

Step 5: Send Follow-Up Instructions Mid-Flight

If the agent is heading in the wrong direction, you can redirect it by typing additional instructions in natural language. For example, you could say “Focus on error handling” or “Expand the scope to include API integration.” The new instruction is sent to the running session, and Copilot adjusts accordingly. This works the same way from your phone as it does on your primary device.

Step 6: Approve or Deny Permission Requests

Sometimes Copilot needs your approval to execute commands or access files. When such a request arrives, you’ll see a prompt on your remote device. You can approve or deny it with a single tap or click. This keeps you in control even when you’re away from your main workstation.

Step 7: Complete the Full Workflow from Anywhere

Remote control doesn’t just let you watch—it lets you take a session from start to finish. For example, using Copilot CLI you could:

1. Scaffold a new feature with /plan on your laptop.
2. Use /remote on to move the session to your phone.
3. Monitor progress and send follow-up instructions while commuting.
4. Review the implementation plan and proposed changes on the mobile app.
5. Create and review a pull request directly from your phone.
6. Merge the PR and move on—all without returning to your desk.

The feature works with any repository and even with directories that aren’t part of a repository, so you can take any coding task wherever you go.

Tips for a Smooth Experience

• Keep your tools updated: Ensure you have the latest version of GitHub Copilot CLI (for CLI users) or the latest VS Code extension. Updates often include performance improvements and bug fixes.
• Use strong network connections: Remote control relies on a stable internet connection. When on mobile, switch to Wi-Fi if possible for faster updates.
• Privacy is built in: Only you can see your sessions. No one else—not even teammates—can access them remotely. The feature respects your repository’s permissions.
• Leverage follow-ups early: Don’t wait until the end to adjust instructions. Provide guidance as soon as you see a deviation; it saves time.
• Combine with GitHub Mobile notifications: Enable notifications for Copilot events so you’re alerted when a session requires your attention (e.g., a permission request).
• Test with a simple task first: If you’re new to remote control, try it on a small script or a minor refactor to get comfortable with the workflow.
• Remember the command: The magic phrase is /remote on. You can also use /remote off to stop sharing a session.

Remote control is more than a convenience—it’s a step toward an end-to-end agentic platform that adapts to your lifestyle. Start using it today and never let a session escape your sight again.