I'm Passing on theGitHub CoPilot CLI Challenge

Source: Dev.to

Why I’m Skipping the GitHub Copilot CLI Challenge

I’m an advocate of AI—both small and large language models—and a fan of dev.to, which I consider the best site of its kind. However, as a Linux user I have to skip this latest challenge because GitHub Copilot is a Microsoft product.

Concerns About the Microsoft Ecosystem

It’s hard to separate a product from its parent company’s broader philosophy. Microsoft’s recent moves—such as the telemetry‑laden Windows 11 release and the forced obsolescence of perfectly functional hardware by ending Windows 10 support—are practices I can’t support.

This extends to GitHub Copilot. It isn’t the agentic nature that bothers me (the ability to view files, directories, and execute commands); it’s that all of this processing happens on Microsoft’s Azure servers, not locally.

As Linux users, we move to distros like Debian or Arch to escape “call‑home” binaries and reject any kind of forced ecosystem lock‑in. I’m simply not installing a cloud‑tethered agent that reports my terminal activity to a central Microsoft server.

Alternatives in Local AI

Again, this isn’t a reflection on dev.to—I enjoy these high‑profile challenges. I’d just prefer the agentic instrument to be different. There is incredible work being done in the local AI space, and we don’t need a cloud connection to have a smart CLI agent on our PC. Open‑source tools like Ollama, Llama.cpp, and local MCP (Model Context Protocol) servers prove that we can have “agentic” help while keeping 100 % of our data on our own silicon.

• Zero Exfiltration: 100 % of the probing stays on your NVMe.
• No Telemetry: No Microsoft account or HTTPS requests to Azure.

Good luck to those taking on this challenge—I’ll be sitting this one out.

Ben S.