GitHub Copilot now works remotely: manage AI dev sessions from anywhere

AI-driven development just became more flexible. GitHub Copilot’s latest update lets developers manage active coding sessions from virtually any device, bridging the gap between the desk and the road.

Seamless sessions across devices

The best AI workflows involve parallel tasks—refactoring code in an IDE, debugging tests in a terminal, and scaffolding new features in the background. Historically, these sessions were confined to a single workstation. Now, GitHub Copilot CLI sessions can be remotely controlled through github.com or the GitHub Mobile app, while IDE integrations expand support to VS Code and JetBrains. This means your coding companion is no longer tethered to your laptop.

Real-time oversight and instant adjustments

Remote control brings transparency to AI-driven development. Start a session in your terminal or IDE, then activate remote mode using /remote on. The session becomes accessible on any connected device, allowing you to monitor progress in real time. You’ll see Copilot’s research plans, file interactions, proposed changes, and executed commands—all unfolding as it happens.

Need to pivot mid-task? Send follow-up instructions using natural language. Redirect an agent veering off course, expand a feature’s scope, or approve permission requests without returning to your primary machine. The ability to steer sessions remotely turns isolated workflows into dynamic, adaptable processes.

End-to-end workflows on the go

Remote control transforms fragmented tasks into cohesive workflows. Begin by planning and scaffolding with Copilot CLI. Use /remote on to transition the session to your mobile app or browser. From there, guide the agent, review implementation plans, and even create or merge pull requests—all from your phone.

This continuity eliminates the friction of switching between tools or surfaces. Whether you’re commuting, traveling, or simply away from your desk, your coding sessions remain under your control.

Built for privacy, designed for productivity

Security remains a priority. Remote sessions are private by default—only you can view or access them. No external exposure means your workflows stay confidential, aligning with organizational security standards.

Getting started is straightforward

No complex setup is required. If you’re already using GitHub Copilot CLI or its IDE extensions, simply start a session and enable /remote on. The feature is integrated and ready to use.

For those new to Copilot CLI, installation is quick. Once active, sessions can be seamlessly transitioned to remote control. Documentation is available for CLI, VS Code, and JetBrains users to guide the process.

Mobile users should ensure their GitHub app is current. Whether on iOS or Android, the latest version unlocks remote session management, making it easier than ever to stay productive outside the traditional workspace.

This evolution marks another step toward a fully agentic development platform—one where AI assistance is as mobile as the developers who rely on it. As remote capabilities expand, the future of coding will increasingly blur the lines between local and distributed workflows.