ローカルのGitHub Copilotセッションをどこからでも操作できるようにTake your local GitHub sessions anywhere

GitHub Copilot workflows

GitHub Copilot sessions started in VS Code or the CLI can now be remotely controlled through github.com and the GitHub Mobile app. This matters when developers need to monitor progress or continue work from their phones after stepping away from their laptops.

The feature supports workflows in which several tasks are happening at once. An agent might be refactoring a module in VS Code while another debugs tests in the CLI and a third scaffolds a new feature in the background.

Remote control

Previously, managing those active sessions was only possible from the developer’s desk. Stepping away from the laptop meant losing visibility into every session that was still running.

Remote control changes that by making local GitHub Copilot sessions available through other surfaces. According to the announcement, remote control for GitHub Copilot sessions started in VS Code or the CLI is now generally available on github.com and GitHub Mobile. Developers can use a phone to check progress and continue the work while away from their computer.

Start a Copilot session

A developer can begin a Copilot session in VS Code or the CLI, then use “/remote on” to make that session available remotely. Once enabled, the session can be accessed through github.com and the GitHub Mobile app.

This allows an existing session to move with the developer rather than remaining visible only on the machine where it began. The same running work can be monitored and continued from another device.

VS Code and JetBrains IDE

The announcement also introduces remote control in VS Code and JetBrains IDE. Together with access through the CLI, github.com, and GitHub Mobile, this makes GitHub Copilot available across multiple surfaces and devices.

The central change is continuity: developers can start work locally, leave their laptops, and retain access to active Copilot sessions from elsewhere.