Look at the VS Code 1.110 release notes, and you’ll see a set of features that read like developer convenience: Agent plugins, hooks, session memory, browser tools. Install a plugin. Run a hook. Persist some context.
Look closer, and something bigger is happening. Microsoft is embedding control plane primitives directly into the development environment — versioned agent configuration, policy enforcement outside model decision-making, shared state across tools, and distribution with organizational review workflows. VS Code isn’t just getting smarter. It’s becoming the platform for teams to configure, distribute, and govern the AI agents that are increasingly doing the work.
Agent plugins, now in preview as part of the February 2026 release, are the most visible piece. A single plugin can bundle any combination of slash commands, agent skills, custom agents, hooks, and MCP servers into an installable package. But the plugin system is just the delivery mechanism. The real story is the full set of capabilities shipping together — and what they mean for how organizations manage AI-assisted development at scale.
What Agent Plugins Bundle
Each plugin can include slash commands, agent skills (on-demand instructions and scripts that load when relevant), custom agents with specialized tool configurations, hooks that execute shell commands at agent lifecycle points, and MCP servers for external tool integrations.
The key design choice: Plugins work alongside your local customizations rather than replacing them. Skills from a plugin show up in the Configure Skills menu. MCP servers appear in the server list. Everything composes.
How Distribution Works
Plugin marketplaces are Git repositories. By default, VS Code discovers plugins from the copilot-plugins and awesome-copilot repos. You can add additional marketplaces using shorthand (owner/repo), HTTPS or SSH git remotes, or file URIs for locally cloned repositories. Private repositories are supported.
That Git-based model means plugins inherit everything teams already have for code: Version control, pull request reviews, branch management, access controls. A plugin update goes through the same review process as a code change. An organization can maintain a private marketplace repository that only its developers can access.
The Broader VS Code 1.110 Context
Agent plugins didn’t ship alone. The full 1.110 release makes the control plane argument hard to ignore.
Hooks let you run shell commands at key agent lifecycle events — enforce policies, auto-lint, block commands before they execute. Programmatic control over what agents can and can’t do, separate from the agent’s own decision-making.
Session memory now persists across Copilot coding agent, Copilot CLI, and code review. Context builds up over time rather than resetting. Plan memory survives compaction.
Chat session forking creates independent sessions that inherit conversation history. Branch from any checkpoint to explore an alternative approach without losing your starting point.
Context compaction supports manual triggers via /compact, allowing you to guide what gets kept.
Browser tools (experimental) let agents drive a browser directly — navigate, click, type, and take screenshots — extending capabilities into UI testing without leaving the editor.
And a new Agent Debug panel helps developers understand what happens during agent runs as customizations accumulate from multiple plugins and local configurations.
The Third Conception of the IDE
Mitch Ashley, VP and practice lead for DevOps and application development at The Futurum Group, sees what’s happening in VS Code 1.110 as far more significant than a set of convenience features.
“Agent plugins, hooks, persistent memory, and Git-based distribution look like developer convenience features. Microsoft’s move here is so much more,” Ashley says. “VS Code is embedding control plane primitives directly into the development environment: Versioned agent configuration, policy enforcement outside model decision-making, shared state across tools, and distribution with organizational review workflows. Platform engineers will own AI agent behavior governance the same way they own infrastructure configuration today.”
Ashley argues this represents a fundamental shift in what the IDE is becoming. “This is the tip of the iceberg. What’s emerging is a third conception of the IDE: Not a workbench, not a smarter workbench, but an agent orchestration platform where developers configure and govern the AI agents that do the work,” he says. “Microsoft is establishing ecosystem gravity before the market recognizes what VS Code has become. The developer role transformation isn’t coming. It’s shipping quietly in preview features.”
Why This Matters for DevOps
Ashley’s framing captures what the individual features obscure. Agent plugins aren’t just a distribution mechanism. Combined with hooks, memory, and the debug panel, they form the governance layer that’s been missing from AI-assisted development.
Right now, AI agent customizations live on individual machines. One developer configures MCP servers. Another writes custom instructions. A third sets up hooks. None of that is portable, shareable, or version-controlled.
Agent plugins formalize the process. A platform engineer can package a standard agent configuration — MCP servers, coding conventions, security hooks — into a plugin that everyone installs. Updates go through code review. Rollbacks work the same way. Audit trails exist because it’s all in Git.
Hooks reinforce the governance angle. Executing shell commands at agent lifecycle points means you can enforce policy outside the AI model’s decision-making — block commands, auto-lint, log tool calls. This is the same principle we saw with IronCurtain’s architecture: Deterministic policy enforcement that doesn’t depend on the model itself.
Infrastructure-as-code replaced ad hoc server configuration with repeatable automation. CI/CD pipelines did the same for builds. Agent plugins and hooks are handling AI agent behavior. The platform engineer’s job is expanding — and the tooling to support that expansion just landed in the editor that 15 million developers already use.
Agent plugins are available now in preview. Enable with chat.plugins.enabled in VS Code 1.110.