Copilot coding agents running on your machine no longer require you to stay at your machine. GitHub just shipped remote control for local Copilot sessions as generally available on github.com and GitHub Mobile.
The practical scenario: you kick off an agent task in VS Code or the CLI, close your laptop, and pick up the session from your phone or any browser.
- Where sessions start: VS Code or the GitHub CLI on your local machine
- Where you can monitor/control them: github.com (web) and GitHub Mobile (iOS/Android)
- How it connects: Each session gets a remote URL via Mission Control — shareable as a link or QR code, per GitHub’s SDK docs
- Multi-agent use case: Run one agent refactoring a module, another debugging tests, a third scaffolding a feature — check all three from a single dashboard
This matters because agentic coding sessions are getting longer. A refactor that takes 20 minutes doesn’t need you staring at a terminal. The remote session model treats Copilot agents more like CI jobs — fire and forget, check results when ready. The difference from GitHub’s cloud-hosted agent sessions is that these run on your hardware, using your local environment and dependencies.
NOTE
Remote sessions are distinct from Copilot’s cloud-hosted compute sessions. Local sessions use your machine’s resources and environment; cloud sessions run on GitHub-hosted infrastructure. The remote URL just gives you a window into the local process.
Available now in the stable channel for all GitHub Copilot users with agent access. No waitlist, no feature flag — connect via VS Code or CLI and the remote URL generates automatically.