Feature request: I want to control Copilot activity on multiple owned machines from the same GitHub Copilot app instance

Feature request: I want to control Copilot activity on multiple owned machines from the same GitHub Copilot app instance.

The main motivation is simply that Copilot requires lots of compute resources to do its work. Well, I have many machines - I can run sessions on each of them concurrently. Today, this requires cumbersome orchestration to actually operate Copilot from each machine locally. The remote steering does not cut it - I want the ability to fully operate each local Copilot (start new sessions etc).

This is also an obvious stepping stone to coordinated Copilot sessions, where a supervisor session on one PC can of its own accord spawn concurrent sessions across a distributed set of Copilot enabled machines connected to my app, so is likely a valuable feature strategically for future expansion of functionality.

There are many ways this could be done but something as simple as a "allow remote control" checkbox on the "server" side + "enter IP+port" on the "client" side would be perfectly fine to satisfy my needs (e.g. with the auth being based on me being logged in on both sides with the same user).

---
| Field | Value |
| --- | --- |
| App version | 1.0.17 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | / |
| Tenure | Day 2 (Week 1) |

Start by reviewing how the GitHub Copilot app currently operates local sessions and provides remote steering. Define how multiple owned machines connect and authenticate, then determine how users start and control sessions on each machine. Done means one app instance can fully operate concurrent sessions across connected machines.

Escrito por el modelo de indexación a partir del texto del issue.