Enabling Remote Access for Copilot CLI Sessions

Enabling Remote Session Access

The remote feature allows developers to access active Copilot CLI sessions from external devices, including mobile phones and secondary computers. To enable this functionality, users must navigate to the GitHub Copilot settings within VS Code and ensure the remote setting is toggled on for the CLI. Once enabled, typing /remote within an active CLI session generates a QR code and a unique URL. Scanning the QR code or visiting the URL allows the user to view and interact with the session state, including all existing context, from a web browser or the GitHub mobile app.

Use Cases and Workflow

This feature is designed for scenarios where a developer needs to monitor long-running agent tasks without remaining tethered to their primary development machine. Because the session runs on the original hardware, it retains access to local environment variables, build tools, and compute resources. Users can initiate a session on their desktop, trigger a task, and then use the mobile interface to check progress, provide follow-up prompts, or steer the agent while away from the desk. The system also supports resuming older sessions, allowing developers to pick up where they left off by running /remote on a previously initialized session to regain access to its historical context.