By ByteBot
Microsoft shipped the Visual Studio May 2026 update on May 26 and buried the real news in a routine changelog: a Plan agent that refuses to touch your code until you’ve approved a written implementation plan. This is not another incremental Copilot improvement. It is the correct model for AI-assisted development, finally arriving in an IDE used by tens of millions of developers.
What the Plan Agent Actually Does
The Plan agent is a separate mode in Copilot Chat — not ask mode, not the existing agent mode. Select it from the mode dropdown, describe your goal, and it starts working in read-only. It scans your codebase, asks clarifying questions about ambiguous requirements, then drafts a full implementation plan as a markdown file. No code changes happen at this stage — none.
Once the plan is drafted, you review it, refine it through chat or by editing the file directly, and only then click Implement plan. That button hands off to Agent mode, which executes against the spec you just approved. The workflow:
- Select Plan from the Copilot Chat mode picker
- Describe your goal (e.g., “add OAuth2 authentication to this app”)
- Copilot scans the codebase and asks clarifying questions
- Copilot drafts the plan — you refine it until it is right
- Click Implement plan to hand off to Agent mode for execution
That checkpoint in step 4 is everything. Every AI agent failure story follows the same arc: the agent made assumptions, dove into the code, produced something plausible-looking but wrong, and the developer spent hours untangling the mess. The Plan agent adds the one thing that prevents this: forced alignment before implementation starts.
The Plan File Is a First-Class Artifact
Plans are saved to .copilot/plans/plan-{title}.md in your project directory. This is not a temp file — it is version-controllable, team-shareable, and persistent across sessions. Copilot updates the file as the plan evolves; you can edit it directly in the editor at any time.
This distinction matters. Compare the three Copilot modes now available in Visual Studio:
| Mode | Writes code immediately? | Plan persisted? | Team-shareable? |
|---|---|---|---|
| Ask mode | Only if you apply | No | No |
| Agent mode (with planning) | Yes | No — temp JSON, deleted on session end | No |
| Plan agent | No, until you click Implement | Yes — .md file in your repo | Yes |
The difference between “planning in agent mode” and the Plan agent is easy to miss. Agent mode built-in planning stores a scratchpad JSON file in AppData\Local\Temp — it is a runtime aid for the model and gets deleted when the session ends. The Plan agent output is a persistent artifact meant to be reviewed, edited, and owned by the team before a single line of code changes.
Multi-File Diff: Table-Stakes, Now Shipping
The May update also ships multi-file summary diff for Copilot edits. When an agent touches ten files simultaneously, the old experience required reviewing each one in a separate tab. The new view shows all changes at once, with accept/reject controls at three levels: all files, per-file, or per individual chunk.
The same unified diff view extends to Git operations — commits, pull requests, and branch history all get an “Open changes summary” button. This ships in Visual Studio 2026 version 18.6. It is functionality that should have existed from the start, but better to ship it alongside the Plan agent than to keep shipping agents without better review tooling.
Skills Panel and Context Window Visibility
Two smaller additions round out the update. The new skills panel, accessible from the tools icon in the chat window, lists every agent skill discovered from your workspace and user profile in one filterable view — previously you had to know a skill existed to use it. The context window ring is a mini donut chart in the chat prompt that shows context consumption at a glance, with a one-click “Summarize conversation” button to compact and reclaim context.
The Right Model, Finally
AI coding tools spent 2024 and 2025 racing to make agents faster and more autonomous, with the implicit assumption that less human involvement meant better developer experience. The developer community pushed back hard on that assumption. The Plan agent is Microsoft acknowledgment that the correct model is: AI explores and proposes, human reviews and approves, AI executes.
Experienced developers have been doing this manually for over a year — describing goals to agents and asking them to draft specs before writing code. Addy Osmani documented the approach in his 2026 LLM coding workflow: “Planning first forces you and the AI onto the same page and prevents wasted cycles.” The Plan agent bakes that practice into the IDE with persistent artifacts, team collaboration, and a clean implementation handoff. That changes how teams can use AI agents together — not just individual developers.
The Plan agent is available now in Visual Studio 2026 and in Visual Studio 2022 version 17.14 or later, with a GitHub Copilot subscription. The multi-file diff view requires Visual Studio 2026 version 18.6.
