The Vibe Father
Visual Studio 2026 now has a public-preview Copilot agent built on the same Copilot SDK used by GitHub Copilot CLI. The July update also adds opt-in skills from Microsoft’s.NET and Azure teams, selected-code review, and organization-level custom instructions.
The four changes that matter
- A new agent. GitHub says the preview agent completes more tasks with less back-and-forth and produces shorter responses.
- Built-in expertise..NET and Azure skills appear when their workloads are installed. They are disabled by default so developers can inspect and enable them.
- Review Selection. Developers can request inline review comments for a selected block and apply or generate suggested changes.
- Organization instructions. Owners can set guidance that applies across repositories in the organization for Copilot Business and Enterprise users.
Why opt-in skills are the right default
A skill can add domain instructions and influence tool use. That is powerful, but a large skill catalog can make behavior less predictable. Opt-in activation lets a team choose the minimum expertise required for a task and review the instruction source before use.
| Control | Recommended practice |
|---|---|
| Built-in skills | Enable per workload and test on representative repositories |
| Organization instructions | Keep concise, versioned, and free of secrets |
| Selected-code review | Use as a second pass, not merge approval |
| Preview agent | Pilot with tests and an easy fallback |
Organization instructions need ownership
Shared guidance can encode testing commands, architecture boundaries, and review expectations once. It can also become stale policy that quietly affects every developer. Assign an owner, review changes through source control where possible, and verify how conflicts with repository instructions are resolved.
Bottom line
The July Visual Studio update makes Copilot more agentic and more customizable. The strongest feature is not automation alone. It is the ability to package reviewed expertise and team rules close to the work. Treat preview behavior as a pilot and keep the compiler, tests, and human reviewer in charge.
