Copilot CLI Remote Control GA: Mobile, Web, VS Code Support

TL;DR

• Remote control for Copilot CLI sessions is now generally available on GitHub Mobile, github.com, VS Code, and JetBrains
• Now supports non-GitHub repositories and directories without repo association
• Monitor, steer, and approve/deny permissions from any device in real time

New

• Multi-surface remote control — Start a Copilot CLI session in your terminal, VS Code, or JetBrains, then monitor and steer it live from GitHub Mobile or github.com
• Non-GitHub repo support — Remote control now works with repositories outside GitHub and standalone directories, visible at github.com/copilot/agents
• VS Code integration — Enable remote control directly from the Chat view with /remote on and manage sessions without leaving your editor
• JetBrains support — Remote control available in JetBrains IDEs alongside VS Code for broader IDE coverage

Key Capabilities

• Track session progress live while away from your desk
• Steer midsession or queue the next message as the current step finishes
• Review and tweak plans before Copilot starts implementing
• Stop a session at any time
• Approve or deny permission requests based on your settings
• Respond to Copilot's questions from anywhere

Getting Started

• Run /update to get the latest Copilot CLI version
• Start a remote session with copilot --remote or enable midsession with /remote on
• Scan the QR code or open the link in GitHub Mobile or github.com
• For longer runs, use /keep-alive to keep your machine awake
• In VS Code, enable the github.copilot.chat.cli.remote.enabled setting and use /remote on in the Chat view
• Copilot Business and Enterprise users: your administrator must enable remote control and CLI policies first

Update GitHub Mobile from the Apple App Store or Google Play Store. For VS Code, download the latest version.

Source: GitHub Changelog