💡 Idea 1: Run Copilot CLI on an Always-On Azure Device¶

Field	Detail
Priority	📌 Important
Status	💡 Idea (not started)
Category	🎓 Learning Project / 💼 Official
Date added	2026-03-28
To-Do link	I1 on To-Do List

The Problem¶

Copilot CLI currently runs on your corp laptop. If the laptop is off, sleeping, or you're away from it, Copilot CLI isn't available. Additionally, if you switch devices (e.g., to a personal device), you need to set everything up again.

The Idea¶

Run GitHub Copilot CLI on an always-on Azure VM (or similar compute) that's accessible from anywhere — your corp laptop, personal laptop, phone, or even a browser. Think of it as your cloud-based Copilot workstation.

Key Questions to Figure Out¶

What Azure compute to use? — VM, Azure Dev Box, Windows 365, or Container?
How to access it remotely? — SSH, RDP, VS Code Remote, browser-based terminal?
How to keep configs in sync? — Same custom instructions, backups, and learning progress across both devices
Cost — What's the monthly Azure cost for an always-on small VM?
Authentication — How does GitHub Copilot CLI auth work on a remote machine?
Dual setup replication — If you change something on local, it syncs to Azure (and vice versa). Could the backup system (OneDrive/Google Drive) serve as the sync mechanism?

Rough Plan¶

Research: Best Azure compute option for a lightweight always-on CLI workstation
Prototype: Spin up a small VM, install Copilot CLI, test remote access
Sync: Set up config replication between local device and Azure device
Document: Create a guide for the full setup (right here on this page!)
Video: Turn it into a YouTube tutorial

Potential Benefits¶

Work from any device, anywhere
Always-on = scheduled tasks (backups) run reliably even if laptop is off
Great demo for customers asking about cloud workstations
Content opportunity: "Run your AI coding assistant in the cloud" video

Next step

When this idea is picked up, the full project documentation will be added to this page as it progresses.