Visual Studio 18.9: org agents, worktrees, and an effort dial

Microsoft's Visual Studio August update post went up on August 25, wrapping the 18.9 release line. Three things in it matter past the release-notes skim: custom agents you publish once for a whole GitHub organization, a thinking-effort dial on Copilot, and native Git worktrees. Together they say the same thing the rest of the tooling market is saying — agent configuration is becoming a versioned team asset, not a personal preference.

What actually happened

Per the Visual Studio 2026 release notes, August update 18.9.0 shipped on August 11, with 18.9.1 on August 18 and 18.9.2 on August 25.

Org-level custom agents. GitHub organization owners can publish custom agents across the org. Visual Studio detects them in eligible repositories and lists them in the agent picker — no per-developer setup, no copy-pasted config file that drifts.

Thinking effort. Supported models now take a low, medium, or high effort setting. Microsoft's framing: low for straightforward suggestions and fewer tokens, medium for everyday work, high for tricky algorithms, architecture calls, and hard debugging. You can also open plan usage from the donut chart in the prompt box.

Git worktrees and submodules. Right-click a branch, pick New Worktree from, and open it in the current window or a second Visual Studio instance. Submodules get a dedicated section in the Git Repository window, read-only by default. There is also a multi-file summary diff and a Git agent that reviews uncommitted changes with inline comments.

Why shared agent config matters for your business

The org-level agent picker is the story. Until now, "our AI coding setup" meant whatever each developer pasted into their own config — which means your standards existed in a group chat, not in the tooling. Publishing an agent at the org level makes the rules an artifact: reviewed, versioned, and applied by default in every repo that qualifies. That is the same move linters made fifteen years ago, and it ended the same argument.

The effort dial is a cost control that finally sits where the decision is made. Every AI coding subscription has a consumption cliff, and the usual response is a policy nobody follows. Putting low/medium/high in the prompt box lets a developer spend deep reasoning on the gnarly migration and nothing on renaming a variable. Pair it with the plan usage readout and you get feedback in the same second as the spend — which is the only kind of budget that changes behavior.

Worktrees are the quiet one. If you have agents doing long-running work, they need somewhere to work that is not your checked-out branch. A worktree per lane — one for the agent, one for you — removes the stash-and-pray dance and makes parallel agent work an ordinary thing instead of a risk.

Sources: Visual Studio Blog, Visual Studio 2026 release notes.