For the past year, the dominant framing in AI coding tools has been IDE-centric: Cursor, Copilot Chat, Windsurf, all living inside the editor, all asking for your approval before touching anything important. The terminal-native, fully agentic model — plan, execute, iterate, ship — was Claude Code’s thesis. Anthropic’s bet that serious autonomous development belongs in the terminal, not nested inside an IDE extension.
On February 25, 2026, GitHub shipped Copilot CLI to general availability. It has an autopilot mode. It runs in the terminal. It delegates to specialized sub-agents. It supports cloud offload. It ships with MCP built in.
Microsoft just published a concession statement, and they formatted it as a changelog entry.
What Copilot CLI Actually Does#
The feature list is not subtle about what this tool is designed to compete with.
Two modes: Plan mode (guided, pauses for human approval at key steps) and Autopilot mode (fully autonomous — executes shell commands, calls tools, iterates on test failures, ships without asking). If you have used Claude Code’s default mode and yolo mode, you know this design.
Specialized sub-agents: Copilot CLI delegates to four internal agents depending on the task — Explore (codebase analysis and search), Task (builds, test runs, iteration), Code Review (diff analysis, issue surfacing), and Plan (implementation strategy). This mirrors the multi-agent architecture that Anthropic’s agent teams work have been developing, with domain-specific agents that hand off to each other.
Cloud offload: Prefix any prompt with & and the task gets delegated to GitHub’s cloud coding agent while your local terminal session stays free. Use /resume to pull the remote session back locally. This is the asynchronous workflow story — start a complex refactor, go do something else, come back when it is done. Claude Code has had async via background agents; Copilot CLI is now matching it.
Multi-model from day one: Claude Opus 4.6, Claude Sonnet 4.6, GPT-5.3-Codex, Gemini 3 Pro. You pick the model per task. This is partly a hedge — Microsoft does not want to be dependent on OpenAI — and partly a genuine acknowledgment that different models have different strengths for different workloads.
GitHub MCP server built in, plus support for custom MCP servers. Given that MCP just crossed 97 million installs and the protocol is effectively the standard now, this is table stakes, but it is worth noting that Microsoft shipped it from day one rather than bolting it on later.
The Timeline That Makes This Significant#
Copilot CLI entered public preview in September 2025. It reached GA on February 25, 2026. The gap between preview and GA was five months — fast by enterprise software standards, and fast by GitHub’s standards specifically.
Compare this to the broader Copilot agentic rollout: agent mode went GA across VS Code and JetBrains in March 2026, with agentic code review (which generates fix PRs automatically, not just suggestions) shipping in the same wave. March 2026 also brought a 50% reduction in coding agent initialization time, via pre-indexing and parallel context loading.
This is not a slow, feature-by-feature IDE evolution. Microsoft is shipping the full agentic stack — terminal tool, IDE integration, cloud agent, code review agent — in parallel, in a compressed timeline. The pace suggests urgency, not roadmap execution.
What This Means for Cursor#
Cursor built a $50 billion business on a single proposition: the best AI-augmented coding experience inside an IDE. Smart autocomplete, inline edits, Composer, chat with codebase context — all of it, beautifully executed, inside VS Code.
The limitation has always been the same: Cursor keeps you in the loop. It is AI-assisted, not AI-autonomous. It asks before it acts. When Cursor shipped self-hosted cloud agents in March 2026 — Brex, Notion, Money Forward running containerized Cursor agents in their own infrastructure — it was the clearest sign yet that even Cursor knows its IDE-only model has a ceiling.
Now Copilot CLI is coming at Cursor from the platform layer. GitHub owns the repository. GitHub owns Actions. GitHub owns code review. Copilot CLI’s cloud offload connects directly to that infrastructure — when the agent runs in the cloud, it has native access to your PRs, your CI runs, your issue tracker. Cursor’s cloud agents have to be configured to integrate with all of that. Copilot CLI comes with it built in.
This is the squeeze: Claude Code pressures Cursor from the autonomy side (truly terminal-native, genuinely agentic, first-class multi-agent support), and Copilot CLI pressures it from the platform-integration side (GitHub-native, repository-aware, CI-connected from day one). Cursor’s strongest argument has always been “the best coding UX.” That argument holds in the editor. It weakens when the editor is no longer the center of gravity.
The Irony Is Not Subtle#
GitHub Copilot launched in June 2021 as an IDE autocomplete tool. It was a VS Code extension. The entire value proposition was: AI in your editor, helping you write code faster, right where you work.
Five years later, GitHub has shipped a terminal tool that can run autonomously without your editor open. They called it “Copilot CLI” — which undersells what it is. It is not a CLI for Copilot. It is a terminal-native agentic coding tool with cloud execution, multi-agent delegation, and autonomous autopilot mode.
The name is the last vestige of the original IDE-centric identity. Everything else about the tool is a repudiation of it.
Anthropic has been building this way since Claude Code launched. The terminal is not a regression from the IDE — it is the right environment for agents that need to run for minutes or hours, call external tools, execute shell commands, manage files, and iterate without a human window managing their lifecycle. Microsoft watched the market shift and shipped accordingly.
What Claude Code’s Lead Actually Is#
None of this means Copilot CLI has caught up. There is a difference between feature parity on a changelog and architectural parity in practice. Claude Code has been running production agentic workflows for longer, has a tighter integration with Anthropic’s safety and context management research, and has the KAIROS daemon architecture (proactive background processing, nightly memory consolidation) that Copilot CLI does not yet match.
But the direction is now unambiguous. The question is not whether the terminal-native agentic model is the future of AI coding tools — Microsoft just answered that. The question is which implementation you trust to run autonomously on your codebase.
For that question, the lead still belongs to the tool that was built for autonomy from the start, not the one that reached GA five months after preview.
Sources: GitHub Changelog — Copilot CLI is now generally available; Visual Studio Magazine — GitHub Copilot CLI Reaches General Availability; GitHub Changelog — Copilot in Visual Studio March update; Awesome Agents — GitHub Copilot CLI Goes Generally Available