A developer reviews an AI coding agent’s progress, test results, and code changes on dual screens.
For ten years, Visual Studio Code wasn't just the most popular code editor on Windows, macOS, and Linux—it was the gravity well of modern software development. Microsoft spent a decade polishing extensions, remote containers, and Git integration until VS Code felt as indispensable to programmers as coffee. Now, Microsoft CEO Satya Nadella has looked straight into the camera and admitted that an upstart terminal tool rattled that dominance in roughly half a year.

Speaking with former Microsoft engineer Gergely Orosz for The Pragmatic Engineer podcast in Redmond, Nadella acknowledged that Anthropic's Claude Code blindsided Microsoft by pulling daily software creation out of graphical editors and straight into the command line. "The thing that hit us was obviously a great work that Anthropic did with their model, which then truly made the CLI as a form factor," Nadella said. "Code went from input to output… In six months or so… IDEs kind of faded away."

Coming from the chief executive of the company that owns Visual Studio Code, GitHub, and GitHub Copilot, that isn't polite conference banter. It is an unusually candid postmortem of how quickly AI-native workflows can outflank even the widest software moat—and why Microsoft is now rebuilding VS Code into something closer to an air-traffic control tower for AI agents.

A developer reviews an AI coding agent’s progress, test results, and code changes on dual screens. How a Terminal Tool Bypassed a Ten-Year Moat​

To appreciate how jarring this shift feels in Redmond, it helps to trace how methodically Microsoft built VS Code's empire—first in the open-source trenches, and later as the launchpad for AI coding assistants.

MilestoneDateStrategic Shift
VS Code PreviewApril 2015Previewed at Build as a free, cross-platform code editor
Open-Source PivotNovember 2015Core codebase open-sourced under MIT license alongside extension support
VS Code 1.0April 2016Reached 2 million installs and more than 500,000 monthly active users
GitHub CopilotJune 2021Brought inline AI code completions directly into the editor
Cursor Fork2023Showed developers would jump to an AI-first fork of VS Code with strong agent mode
Claude Code PreviewFebruary 2025Anthropic launched an agentic CLI tool on Feb. 24, skipping the GUI editor altogether

Nadella credited VS Code's original rise to "building in the open," recalling how product managers read community feedback daily alongside early leads like Erich Gamma and Amanda Silver. For years, that flywheel looked untouchable. Even when Cursor forked VS Code in 2023 and introduced a fast, multi-file agent mode, Microsoft was fighting on familiar turf—inside a window full of file trees, tabs, and syntax highlighting—and quickly worked to match Cursor's agent features inside Copilot.

Claude Code changed the playing field by walking right past the editor. When Anthropic introduced Claude Code as a limited research preview on February 24, 2025, it didn't ask developers to switch themes or learn a new IDE; it ran in the terminal, where it could read codebases, edit files, write and execute tests, run shell commands, and push commits to GitHub while keeping a human in the loop.

Orosz framed the disruption in stark historical terms on X, comparing VS Code's long strategy to a modern "Embrace, extend, extinguish" playbook—make an open-source editor so good that rivals can fork it, yet never quite catch Microsoft's ecosystem—only to watch a command-line agent undercut the premise. "Claude Code destroyed this bulletproof strategy meant to work for decades… in less than 6 months," Orosz wrote. Or, as one developer reply quoted by Windows Latest put it: "10 years building the perfect moat and someone just walked around it in a terminal."

Nadella's takeaway from the ambush was blunt: "When model jumps happen nonlinearly, the form factor has to change quickly. AI-first product building in that sense is unforgiving," he told Orosz. "Don't be in love with what you built."

That candor echoes what Microsoft insiders have been signaling for months. Back in early September 2026, 18-year Microsoft veteran and Distinguished Engineer David Fowler sparked a storm on X by declaring, "Typing code is absolutely over." Fowler wasn't claiming software engineers are obsolete; rather, as tools like GitHub Copilot's coding agent and Microsoft's Aspire toolchain let agents spin up Windows or Linux environments, inspect logs, and open pull requests autonomously, human labor shifts upward toward architecture, specifications, and review.

Section summary: Microsoft spent a decade turning VS Code into the default developer workspace, only for stronger reasoning models to make terminal-based agents viable almost overnight. The disruption wasn't another prettier editor—it was discovering that once code becomes an output rather than a manual input, many developers stop staring at an editor at all.

Are Developers Really Abandoning VS Code? What the Data Actually Shows​

If you spend ten minutes scrolling through developer feeds right now, you'd swear nobody opens an IDE anymore. Orosz noted that among ten startup developers he spoke with—himself included—none were coding inside an IDE the way they did a year earlier, and some joked about leaving VS Code open in the background purely for the familiar developer aesthetic. Even non-developers are feeling the shift: Windows Latest's Abhijith M B noted that Claude built him two native WinUI 3 Windows apps this year—a media downloader and a music player—requiring Visual Studio only occasionally at the end to package them.

Before writing VS Code's obituary, though, let's check the actual scoreboard. Because developer anecdotes travel faster than survey methodology, the numbers tell a much more nuanced story than "everyone uninstalled VS Code."

  • VS Code is still #1 by a landslide: In Stack Overflow's 2026 Developer Survey (released October 6, 2026, across 30,903 valid responses), 70.9% of the 13,193 respondents answering the development-environment question reported using VS Code regularly over the past year. Second place went to Notepad++ at 27.8%, followed closely by Microsoft's full Visual Studio IDE at 27.6%, Vim at 27.2%, IntelliJ IDEA at 24.3%, and Cursor at 14.9%.
  • Mind the 2025-to-2026 survey comparison: Commentators have pointed to VS Code slipping from 75.9% in Stack Overflow's 2025 survey to 70.9% in 2026 as a dramatic drop. While that five-point dip is real on paper, Stack Overflow also changed its questionnaire in 2026—removing terminal agents like Claude Code (which sat at 9.7% in the 2025 IDE table) from the editor list and moving them into a dedicated AI coding agents category.
  • Claude Code leads the agent category, while Copilot stays huge: Among the 12,255 respondents to Stack Overflow's 2026 AI coding-agent question, 65.5% said they had used Claude Code in the past year, beating GitHub Copilot (58.7%), OpenAI Codex (29.5%), and Cursor (25.5%). Meanwhile, Microsoft reported 50 million GitHub Copilot users as of July 2026, and JetBrains' weighted developer surveys showed workplace Claude Code usage climbing from roughly 3% in mid-2025 to about 39% by mid-2026.

Crucially, Stack Overflow's questions measure whether a developer used a tool over the past year—not how many hours a day they spend typing inside it. That distinction explains how two seemingly contradictory facts can both be true: 70.9% of surveyed developers still keep VS Code in their toolkit, even as many spend far fewer keystrokes inside it.

And for plenty of engineers, closing the IDE completely is still reckless. Critics of hands-off "vibe coding" point out that reviewing multi-file diffs, untangling AI-generated "slop," editing Markdown specs, and auditing sensitive paths are miserable in a bare terminal or web PR view. As one developer put it bluntly online: "Money, auth, permissions, DB code? I read every line. That's where my IDE still lives."

Section summary: VS Code hasn't lost its user base—at 70.9% regular usage in Stack Overflow's 2026 survey, it remains the dominant desktop development environment. What Microsoft is actually losing is active developer attention as terminal agents led by Claude Code handle the first-draft grunt work outside the editor.

Inside Microsoft's Counter-Move: VS Code 1.146 and 1.147​

If developers won't sit in VS Code to type line-by-line syntax anymore, what does Microsoft want them doing inside the app? Judging by two rapid-fire stable updates shipped in November 2026—VS Code 1.146 on November 11 and VS Code 1.147 on November 18—Redmond is turning its editor into an orchestration cockpit for AI agents, including rivals.

The architecture pivot has been building all fall, and these two releases make Microsoft's direction unmistakable:

  1. Saying goodbye to the old Local harness (VS Code 1.146): Since version 1.143, Microsoft has defaulted new sessions to the Copilot harness, which runs through an Agent Host so sessions can persist in the background and obey enterprise sandbox and permission policies. In 1.146, Microsoft officially deprecated the legacy Local harness and scheduled its removal for February 2027.
  2. An "Inbox" for juggling parallel agents (VS Code 1.146): Instead of watching one cursor blink, developers running multiple background tasks get an experimental Inbox mode in the Agents window that surfaces sessions needing human input while letting you snooze or hold others, alongside preview Chat windows that tear chats out into standalone layouts and preview Model comparison tools.
  3. Bridging the CLI gap (VS Code 1.146): Recognizing that developers love starting in a terminal, Microsoft added an experimental /code handoff command in GitHub Copilot CLI (1.107 or later with experimental settings enabled) that exits the terminal session and resumes the exact conversation, history, and mode inside VS Code.
  4. Scheduled and drafted agent work (VS Code 1.147): Experimental Send Later lets you schedule local agent prompts—say, checking a build after it finishes or queuing a morning review—so long as the local agent host stays awake, while experimental Draft requests let you park multiple half-written prompts with their workspace and model settings intact.
  5. Model routers and "hybrid intelligence" (VS Code 1.147): Rather than forcing one model for every job, experimental Model routers (enabled via chat.copilot.modelRouter.enabled and defined as YAML files in ~/.agents/model-routers/) use a decision model (gpt-6-luna-decisions) to automatically send each prompt to the preferred model you've configured for that kind of work.
  6. Browser control and visual reviews (VS Code 1.147): A preview Browser Use integration lets Copilot harness sessions drive your default Google Chrome or Microsoft Edge browser—reusing existing logins while still prompting for site access and leaving sign-ins to the human—provided you install the GitHub Copilot browser extension, have Node.js 22 or newer on your PATH, and enable chat.agentHost.browserUse.enabled. Agents can also render inline HTML previews and experimental charts inside the Agents window.

Most tellingly, VS Code isn't trying to lock competitors out of the party. Enterprise administrators using vscode.allowedHarnesses in 1.147 can explicitly permit Claude and Codex sessions right inside VS Code alongside Copilot—though Microsoft's release notes include an important security caveat for IT teams: Claude and Codex sessions run without Copilot's managed permission rules, sandboxing, MCP controls, or plugin restrictions.

Verification, "Insider Risks," and the Rebirth of the IDE​

Nadella doesn't believe the graphical IDE is permanently dead. Instead, he told Orosz that as code generation grows cheap and abundant, the hard engineering bottleneck shifts to specifications and verification—making sure an agent didn't pass a test suite simply by deleting a failing test.

In that world, Nadella imagines a "rebirth" of the IDE centered less on typing boilerplate and more on authoring intent—"how do I really input the specs and the markdowns"—while building independent verification loops around agent behavior. He even urged enterprises to avoid single-vendor lock-in by decoupling their harness, memory, and model layers, to consider open and local models ("hybrid intelligence" that routes routine work to laptops and desktops before hitting the cloud), and to treat autonomous agents as "insider risks" requiring strict boundaries and audits.

He also pointed to Microsoft's own internal upheaval. Asked about historic voluntary exit offers extended to software engineers across Microsoft's roughly 200,000-person workforce, Nadella admitted he couldn't promise roles would stay the same, noting that even internally, not every team had "got the memo" on reorganizing around AI-native workflows. At the same time, he cautioned against writing off junior talent during a temporary hiring slowdown, pointing to Microsoft's new PRAISE preceptorship program with Carnegie Mellon University—modeled on clinical nursing mentorship—to pair seasoned engineers with newcomers on systems thinking, judgment, and AI oversight.

From a skeptical observer's chair, there's plenty of healthy tension in Microsoft's pitch. Experimental model routers, preview browser hooks, and early agent inboxes won't immediately lure back engineers who already live comfortably inside a fast tmux pane with Claude Code. And enterprises will rightly hesitate before flipping on third-party agent harnesses inside VS Code if those harnesses bypass managed sandbox guardrails.

Yet Microsoft's strategic pivot is crystal clear. If coding really has shifted from writing lines to directing and verifying fleets of agents, VS Code doesn't need to win the battle for every keystroke. It just needs to remain the place on your Windows desktop where the specs are written, the diffs are audited, the agents are kept on a leash, and the final shipping decision gets made.

 

References

  1. Claude 3.7 Sonnet and Claude Code \ Anthropic anthropic.com
  2. Visual Studio Code 1.146 code.visualstudio.com
  3. Visual Studio Code 1.147 code.visualstudio.com