Support Microsoft Dev Box connections through Dev Tunnels

Current workflow

My codebase and build environment live on Microsoft Dev Boxes. I connect from local VS Code using the Dev Box extension and run Copilot CLI in the remote terminal.

I'd like to use the GitHub Copilot app in the same way, without running the app inside the Dev Box over Remote Desktop, where latency makes the UI less responsive.

Requested functionality

Support connecting the local GitHub Copilot app to a Microsoft Dev Box through Dev Tunnels, similar to the VS Code Dev Box extension:

• Keep the Copilot app UI on my laptop.

• Run agent sessions, commands, and builds on the Dev Box.

• Work with repositories and tools already available on the Dev Box.

• Handle tunnel discovery and authentication in the app, without requiring a separately configured SSH server or inbound firewall changes.

Why this would help

This would let me use the Dev Box's compute resources and existing development environment while keeping the UI responsive locally. It would also avoid maintaining a separate remote-access setup just for the Copilot app.

Start by reviewing how the VS Code Dev Box extension handles Dev Tunnel discovery and authentication, then locate the Copilot app's existing remote-session and terminal entry points. Done means the local UI can connect to a Dev Box, run agent sessions, commands, and builds there, and use its repositories without a separate SSH server or inbound firewall changes.