There’s a mental model that most developers still carry: a code tool is something you sit in front of. You open the terminal, launch the session, watch it work. The moment you step away, collaboration stops.
Copilot CLI just ended that model.
On April 13, GitHub launched copilot --remote in public preview — a feature that streams your active CLI session to GitHub on the web or GitHub Mobile in real time. You launch the agent, it starts working, and you leave. From your phone, from a browser tab, from anywhere, you log in to see how it’s going, guide it if needed, and let it continue.
This isn’t remote execution in the traditional DevOps sense. The process still runs on your local machine. What changes is the interface layer: instead of being physically present at the terminal, you supervise the session from wherever you are.
What You Can Actually Do from the Remote Interface
The remote view isn’t read-only. Once you open the session link (or scan the QR code the CLI shows), you have full steering capability:
- Send follow-up instructions — during the session or once the current turn ends
- Review and modify plans before implementation starts
- Switch modes between plan, interactive, and autopilot
- Approve or deny permission requests based on your existing CLI configuration
- Respond to
ask_userprompts — when the agent needs a decision, you make it from your phone - Stop the session completely if something goes off track
Each action stays synchronized between the terminal and the remote client. The session is private — only visible to the user who started it. For long tasks, /keep-alive prevents your machine from entering sleep mode in the middle of execution.
To get started: run /update to get the latest CLI version, then launch with copilot --remote or enable it in an existing session with /remote. One requirement: your working directory has to be a GitHub repository. Mobile access is available through a beta on Google Play and iOS TestFlight.
For Copilot Business and Enterprise users: an administrator needs to enable remote control and CLI policies before this feature is available to you.
This Follows a Pattern That’s Already Becoming Standard
Claude Code introduced remote access to active local sessions earlier this year. Within weeks, Copilot CLI users were already submitting requests asking for the same thing — explicitly citing Claude Code’s implementation as a reference point. “It would be amazing — something like Claude Code’s remote control feature for Copilot CLI,” one user wrote in a GitHub community discussion. Six weeks later, that request was granted.
That timeline matters. It’s no coincidence. It’s competitive convergence around a workflow pattern developers clearly want: long-running autonomous agent sessions that don’t require you to watch the terminal the whole time.
The implication is bigger than convenience. When agents run for 20 or 30 minutes on a task, the assumption that a developer is staring at the screen that entire time stops making sense. Remote supervision — logging in to see, guide, approve, continue — is becoming the real interaction model for agentic development.
What This Means for How Teams Work
From a governance perspective, this shift is significant. Approval flows that currently require physical presence at the terminal can now happen asynchronously. A developer running a long refactor or migration can delegate supervision to a colleague, continue guiding the process from a meeting, or handle a critical approval from the airport.
The next step — which developers are already building on their own — is integrating these approval flows into existing messaging channels. There are reports from the developer community of people connecting Copilot to Telegram to handle approvals remotely, or asking for push notifications when the agent needs input. GitHub’s own recommendation to use /keep-alive is a telling signal: they’re designing for tasks long enough that you step away and come back later.
The code agent is no longer just a terminal tool. It’s becoming something more like a background worker with an approval queue — and the interface for that queue is wherever you are.
Have you tried copilot --remote yet? How are you handling long Copilot CLI sessions? Let us know in the comments. 