Microsoft just updated Visual Studio Code with a confusing new feature called Agent HQ, a preview of TypeScript 7, and the end of IntelliCode. If you use VS Code daily, at least one of these changes will affect how you work.
The most significant push is around agentic coding. Microsoft wants multiple AI agents working in the background while you code. They’re calling the initiative Agent HQ, but the surrounding messaging is messy.
The Agent HQ Confusion
VS Code’s release notes tout Agent HQ as the first prominent feature in this update. But then the term appears again only briefly in the documentation. A GitHub post clarifies that Agent HQ isn’t actually a feature—it’s a direction. Microsoft wants to integrate agents from multiple vendors into your coding workflow.
The actual feature is the Agent Sessions view, which lets you see multiple background agents working at once. But here’s where it gets weird: this view is now disabled by default. Microsoft released a video earlier this week showing off Agent Sessions with genuine enthusiasm. Days later, they disabled it in the release.
Why? Because agent sessions are now integrated into Chat instead. You can re-enable the standalone view if you want, but Microsoft plans to remove it entirely in a future release.
That’s not great communication. Teams trying to understand what Agent HQ actually means will find conflicting information depending on where they look.
What Actually Works
Beyond the naming confusion, the agent updates include some useful capabilities. You can now keep agents running even when chat is closed. You can move agent sessions from local to the cloud. There’s support for custom subagents and sharing agents across your organization.
Ten new agent features shipped in this update. The technology itself works. Microsoft needs clearer messaging about what they’re building and why.
The Security Problem Nobody Wants to Talk About
AI agents create real security risks. Prompt injection attacks can trick agents into executing malicious instructions. And generative AI makes mistakes—Google’s Antigravity agent recently wiped an entire hard drive partition.
VS Code includes a setting called YOLO (you only live once) that disables manual approval for all tools in all workspaces. The setting description warns that “this feature disables critical security protections and makes it much easier for an attacker to compromise the machine.”
So why does this setting exist at all? If it’s harmful, remove it. Don’t give users the option to shoot themselves in the foot.
The YOLO setting reveals the tension between Microsoft’s desire to compete in the AI agent market and basic security practices—speed matters in competitive markets. But security matters more.
TypeScript 7 Brings Real Performance Gains
The TypeScript 7 preview is legitimately exciting. Microsoft rewrote the compiler and language service in Go to achieve native-code performance. According to principal product manager Daniel Rosenwasser, developers can expect faster load times, less memory usage, and more responsive editing.
This is a substantial rewrite. TypeScript has been around for over a decade. Rebuilding the core toolchain in a different language takes serious commitment. The fact that they’re previewing it now means the work is far enough along to test in real projects.
You’ll need TypeScript Go installed and configured to try the preview. But if you work in TypeScript regularly, the performance improvements will be noticeable.
VS Code’s own build scripts now run entirely in TypeScript, rather than a mix of TypeScript and JavaScript. That’s possible because Node.js 22.18 and higher support TypeScript natively. It shows how much TypeScript has matured as a development language.
IntelliCode Dies, Copilot Subscriptions Live
Here’s the change that will annoy people most. Microsoft is deprecating IntelliCode, which provided free AI-assisted code completion for Python, JavaScript, TypeScript, Java, and C#.
IntelliCode used a local model. No cloud dependencies. No subscriptions. It just worked. Over 60 million developers installed it, and the ratings are strong.
Now Microsoft wants you to use GitHub Copilot instead. You get 2,000 free completions per month. After that, you need a subscription.
One user asked in the reviews: “Why is this extension being deprecated and being migrated to Copilot?” The answer seems obvious. Subscriptions generate revenue. Free features don’t.
VS Code is open source. Many features are free. But Microsoft still drives the roadmap with commercial goals in mind. IntelliCode becoming a paid feature through Copilot is a clear example of that tension.
Language servers will still provide basic code completion and syntax highlighting. But the AI assistance that came free with IntelliCode now requires a subscription. That’s a significant change in value proposition.
“It is not unusual, or even surprising, to see technology companies reverse course on features, naming, or release plans, especially at the pace AI innovation is moving. What we are seeing in VS Code reflects a broader industry reality in which vendors must rationalize overlapping products, experimental capabilities, and new messaging as AI is layered onto mature platforms,” says Mitch Ashley, VP and practice lead, software lifecycle engineering, The Futurum Group. “Microsoft is not alone in this. Google and AWS are navigating similar complexity, each in its own way, as they balance speed, clarity, and market pressures.
What This Means for Development Teams
If your team relies on IntelliCode, start planning the transition. Decide whether Copilot subscriptions make sense for your budget and workflow, or if basic language server completion is sufficient.
If you’re exploring agentic coding, understand the security implications before enabling agents in production environments. Don’t touch the YOLO setting. Ever.
And if you work heavily in TypeScript, try the TypeScript 7 preview. Real performance improvements are worth testing early.
This will probably be the last major VS Code update until February 2026. Microsoft skips the December release cycle. That gives you time to evaluate these changes before the next round of updates arrives.
The move toward AI agents is inevitable. The subscription model for AI features is inevitable, too. But teams should make those transitions deliberately, understanding the costs and trade-offs involved.