Azure-hosted headless Copilot for persistent, cross-device coding sessions

Idea

Support running gh copilot as a persistent, headless coding host on an Azure VM, with the Copilot client connecting to it seamlessly. Think of it as a cloud VM for coding: the workspace and agent live remotely, and you can access the same sessions from anywhere.

Why

A coding session tied to one computer is awkward to resume from another. Switching devices should not require recreating the development environment or losing session context, and closing a laptop should not interrupt work running on the remote host.

Proposed experience

• Provision or attach an Azure VM as a headless Copilot host.
• Keep repositories, toolchains, terminals, running tasks, and session state on that host.
• Connect securely through the Copilot client, with the familiar session, code review, and approval workflows.
• Disconnect and reconnect from another device to continue the same session, preserving conversation history and workspace state.
• Allow host-side work to continue while the client is disconnected, without bypassing required approvals, and provide explicit controls to stop work or shut down the VM.

Example

Start coding on a laptop, leave a long-running task on the Azure host, then open Copilot on another machine to review the results and continue in the same workspace.

The goal is a persistent remote coding environment integrated with the Copilot client, not just a fresh VM per task or a full remote desktop.

The issue names no files, tests, or entry points to begin with. Start by reviewing the Copilot app's existing client, session, approval, and workspace architecture, then determine how Azure VM provisioning and persistent reconnection would fit. Done would require an agreed design and an end-to-end implementation covering host lifecycle, secure connections, session persistence, approvals, and client reconnection.