My dev flow involves multiple VMs running instances of GH Copilot App.

My dev flow involves multiple VMs running instances of GH Copilot App. I'm switching between them as I query for changes, tests, builds, etc. This keeps my work sandboxed.

It would be very cool to allow my "main" GH Copilot app on my laptop connect to these so that I don't need to open RDPs just to only use the app. If these could be handled by the "sessions" section somehow, it would make my flow much easier to see at a glance. IF I need more details I could go into the machines, but I get terminal, MD previews, and cool tools.

This could allow for an agentic flow that manages GHC apps in various VMs that run their own stuff.

---
| Field | Value |
| --- | --- |
| App version | 1.0.24 |
| OS | Windows 10.0.26200 |
| Theme | Noctis Azureus |
| Path | /chat |
| Tenure | Week 2 |

No files or tests are named. Start by reviewing how the Sessions section represents and connects to app instances, then clarify the supported VM or RDP connection model and lifecycle. Done should include a defined multi-VM experience visible from the main app, with acceptance criteria for connecting to and switching among remote instances.

Written by the indexing model from the issue text.