GitHub Copilot CLI Gets Remote Sessions on Web and Mobile

GitHub has added a major new capability to Copilot CLI: remote session control. With the new copilot --remote mode, a CLI session can be monitored and steered from GitHub on the web or through the GitHub Mobile apps.

That changes the Copilot CLI from a purely local tool into something much more flexible. Instead of staying tied to the terminal that launched it, a running session can now surface a live link and QR code that let you open it on another device, follow progress, and send follow-up instructions as the session runs.

What remote sessions do

The remote experience keeps the CLI and GitHub in sync in real time. Actions taken from the terminal appear on the web view, and actions taken from the web or mobile view flow back into the session.

GitHub says remote sessions support the same kinds of interactions people already rely on in Copilot CLI, including:

• sending steering messages during a session
• continuing a session once the current turn finishes
• reviewing or changing plans before implementation begins
• switching between plan, interactive, and autopilot modes
• stopping the session entirely
• approving or denying permission requests based on existing CLI settings
• responding to questions raised through the ask_user flow

Why this matters

Remote control is useful for anyone who wants more flexibility while working with Copilot CLI. You can start a task on your laptop, check on it from a browser later, or keep an eye on longer-running work from your phone.

It also helps when you want to stay involved without staying glued to the terminal. That is especially handy for longer implementation tasks, planning sessions, or workflows that require occasional human approval.

Getting started

GitHub recommends updating to the latest CLI version first, then starting a session with copilot --remote or enabling remote mode in an existing session with /remote.

A few requirements and notes are worth keeping in mind:

• your working directory needs to be a GitHub repository
• remote sessions are private and only visible to the user who started them
• Copilot Business and Copilot Enterprise users may need an administrator to enable the required policies first
• GitHub also suggests using /keep-alive for longer tasks so your machine does not sleep while the session is running

The bigger picture

This update moves Copilot CLI closer to a cross-device workflow that feels more like a live session than a local command-line tool. For developers, that means more continuity, more control, and fewer interruptions when work needs to move between desktop, browser, and phone.

For teams already using Copilot CLI, remote sessions could make it easier to collaborate around the agent’s progress, especially when a task needs quick feedback or a decision before it can continue.