Microsoft shipped three Visual Studio Code updates in rapid succession between June 24 and July 8, 2026, packing the releases with agentic AI capabilities that, in many developers' eyes, overshadow conventional editor improvements. InfoWorld senior writer Serdar Yegulalp publicly called out the shift, complaining that VS Code is \"fast becoming an agent front end first, and everything else is a distant second.\" The good news: every one of these new AI features can be turned off, either by individual users or through enterprise policies. Here’s what landed, what it means for your workflow, and exactly how to tame the new AI defaults.

AI Agents Take Center Stage in Three Consecutive Updates

VS Code’s rapid-fire summer releases concentrated heavily on agent infrastructure, browser integration, and model management—leaving traditional editor enhancements in the minority.

Version 1.126 (June 24) introduced session-level AI cost reporting, multiple chats in a single agent-host session, agentic code-review feedback, and the new Agent Host Protocol. The one non-AI concession: opening unfamiliar folders now defaults to Restricted Mode rather than immediately prompting users to trust them.

Version 1.127 (July 1) pushed integrated browser tools to general availability. Agents gained the ability to open web pages, inspect content and errors, capture screenshots, and navigate applications—all natively. The release also added agent session groups, pull-request feedback actions, automatically generated PR descriptions, and agent credit visibility. On the management side, Microsoft introduced file-based managed Copilot settings on Windows via %ProgramFiles%\GitHubCopilot\managed-settings.json, enabling policy enforcement without MDM.

Version 1.128 (July 8) refined multi-chat agent workflows and made image support in Chat generally available. Yegulalp noted the single broadly useful non-AI enhancement: OS-level keyboard-shortcut registration. Everything else in the changelog continued the agent theme.

What These Changes Mean for Developers and Admins

The practical impact depends on your role and how you use Visual Studio Code.

For Individual Developers

AI is entirely optional. If you prefer a traditional extension-driven editor, you can disable the entire AI stack with one setting. The core editing experience—syntax highlighting, IntelliSense, debugging, and language extensions—remains untouched. Power users who do want agent assistance get new capabilities: browser automation for testing, multi-chat sessions that can iterate on code, and image analysis in chat. The key is that you choose.

For System Administrators and IT Pros

This is where the updates demand attention. The new agent features can reach project files, execute terminal commands, spin up browser sessions, and—if permitted—access network resources. An agent that misbehaves or is misconfigured could damage source code or exfiltrate data. Organizations using GitHub Copilot should align these new capabilities with existing data-handling rules. Microsoft provides granular controls to disable agent mode, restrict network access, block third-party tools, and limit MCP server connections. Deployable policies exist both via Group Policy/MDM and through the new file-based managed settings.

For Power Users and Tinkerers

The agent layer is powerful but needs deliberate configuration. Browser tools, for example, can automate end-to-end testing or scrape documentation, but an agent with unrestricted terminal access is a risk. Treat agent permissions the same way you’d treat any shell extension: grant only what’s necessary.

The Gradual Infusion of AI into VS Code

VS Code’s AI journey didn’t start with agent mode. GitHub Copilot first appeared as an extension in 2021, offering inline code completions. In 2022, Copilot Chat entered preview, and by 2023 Microsoft embedded chat directly into the editor’s sidebar. Early 2024 brought experimental agent concepts, and throughout 2025 those experiments expanded into multi-step workflows and tool use.

The releases tracked by this story mark a tipping point. Versions 1.126 through 1.128 move agents from optional preview to built-in default, with the Agent Host Protocol providing a standard interface for autonomous coding assistants. Microsoft’s documentation now describes VS Code as shipping with AI agents—a significant rebranding of what was once just a code editor.

The InfoWorld piece captured a growing sentiment: for developers who adopted VS Code because it was fast, extensible, and lightweight, the AI focus feels like a bait-and-switch. But Microsoft argues the extensibility model still works, and AI is simply one more extension of that philosophy.

How to Disable AI Features and Regain Control

Turning off AI in VS Code is straightforward, whether you’re on a single machine or managing a fleet.

For Individual Users

  1. Open Settings (Ctrl+,) and search for chat.disableAIFeatures.
  2. Check the box to disable built-in chat, inline suggestions, and Copilot extensions.
  3. Restart VS Code to apply the change.

Alternatively, edit settings.json directly and add:

\"chat.disableAIFeatures\": true

To disable only specific AI features, look for:
- github.copilot.enable (set to false)
- inlineSuggest.enable (set to false)
- chat.enabled (set to false)

For Enterprise Administrators

  • Disable AI entirely: deploy the chat.disableAIFeatures setting via Group Policy, MDM, or the managed-settings file.
  • Disable agent mode specifically: set chat.agent.enabled to false.
  • Restrict agent network access: set chat.agent.networkAllowed to false.
  • Control MCP servers: use chat.agent.mcpServers to allow or block specific endpoints.
  • Deploy file-based settings on Windows: create %ProgramFiles%\\GitHubCopilot\\managed-settings.json with the desired configuration overrides. Example:
    json { \"chat.agent.enabled\": false, \"chat.disableAIFeatures\": true }

These policies do not remove the AI code from the product; they simply prevent the features from activating. All core editing functionality, extensions, and debuggers continue to work exactly as before.

What to Watch as VS Code Evolves

The InfoWorld criticism has amplified a debate that’s been simmering in the developer community: should an editor’s development resources tilt so heavily toward AI, or should Microsoft invest equally in core IDE improvements? For now, Microsoft shows no sign of pulling back—the next Insider builds already hint at deeper agent integration. But community feedback has shaped VS Code’s trajectory before. If enough users request a “classic mode” or a clearer separation between editor and agent features, the roadmap could shift.

In the meantime, the tools to carve out a traditional coding environment are already in your hands. Whether you embrace the agents or shut them down, you get to decide exactly how much AI lives in your IDE.