A futuristic AI development dashboard connects code, model choices, security checks, and deployment in a glowing interface.
GitHub's changelog went up on October 22, but the update itself is older. Microsoft's own roundup ran on September 29 and pointed developers to the Visual Studio 2026 Stable Channel. This is Visual Studio 2026's September wave of Copilot features. It has three parts: pull-request exploration through the Git agent, a reworked Bring Your Own Model (BYOM) preview, and a Copilot fixer for vulnerable NuGet packages.

One of the three is a breaking change. If you run local models, read the BYOM section first.

A futuristic AI development dashboard connects code, model choices, security checks, and deployment in a glowing interface. The short version​

FeatureWhat it doesKey prerequisite
Git agent PR explorationSummarizes a pull request, with links to its comments and filesGit provider MCP servers connected (GitHub and Azure DevOps supported)
BYOM (preview)Runs Copilot's agent on models you chooseThe new Agent (Preview); provider set up
NuGet Audit fixerStarts a Copilot-driven fix for vulnerable packagesSigned in to GitHub Copilot; NuGet MCP server enabled

The GitHub changelog says the update is available on all Copilot plans: Free, Student, Pro, Pro+, Max, Business and Enterprise. Don't confuse that list with the BYOM edition list, which covers Visual Studio SKUs (Community, Professional, Enterprise) and not Copilot plans.

Bring Your Own Model: the headline, and the catch​

BYOM lets you use the models your team prefers. That can be through GitHub Copilot or your own deployments, and it works whether or not you're signed in to GitHub. It is a preview, and it is on by default in Community, Professional and Enterprise.

Supported providers are Microsoft Foundry, OpenAI, Anthropic and Ollama. Custom endpoint support covers OpenAI and Ollama.

Setup

  1. Open Chat.
  2. Open the model picker and choose Add a model or Manage Models.
  3. Connect to your provider.
  4. Work in the new Agent (Preview).

The breaking change​

BYOM now works only with the new Agent (Preview), which is built on the GitHub Copilot SDK-powered harness. The earlier BYOM experience in the previous Ask and Agent modes is no longer supported. Microsoft says previously added Ollama models must be re-added after the update because of backend changes for that provider. Neowin and Windows Report both say you can do this through Chat > Model Picker > Manage Models.

If a local Ollama setup suddenly looks empty after updating, that is why. Nothing is broken. Re-add the models.

Preview caveats​

Microsoft is open about the limits. Product manager Mark Downie wrote that not every model supports every Agent Mode capability yet. He added that Visual Studio marks unsupported features clearly instead of failing silently. "Supported provider" therefore doesn't mean every model gets feature parity. Test your chosen model on real tasks before you standardize on it.

What this doesn't give admins yet​

Microsoft's August 24 BYOM preview post said enterprise management features were still to come. Those include an ADMX policy to disable BYOM for Professional and Enterprise users, centralized model configuration, and finer controls such as context size and tool calling. The post tied the ADMX policy to the 18.10 GA release. The September update material doesn't confirm that any of these shipped.

BYOM is also on by default. Admins in regulated shops should check what developers can connect to before the governance tooling arrives. That is my inference from the preview's status, not a Microsoft statement.

Fixing vulnerable NuGet packages from the Error List​

Microsoft's blog documents the flow. After a restore reports NU1901, NU1902, NU1903 or NU1904, you select the sparkle action in the Fixer column. That opens GitHub Copilot Chat in agent mode and asks Copilot to fix the vulnerable packages using the NuGet MCP server.

Steps

  1. Restore a solution that contains a package with a known vulnerability.
  2. Open View > Error List and find the NuGet Audit warning.
  3. Select the sparkle action in the Fixer column.
  4. Review and apply the changes Copilot proposes.

Prerequisites

  • You must be signed in to GitHub Copilot. BYOM's sign-in flexibility does not extend to this feature.
  • The NuGet MCP server must be enabled. Microsoft Learn says it is built into Visual Studio 2026 but must be enabled once. Open Copilot Chat while signed in, click the tools icon, and tick the server named "nuget".

Common failure points

  • Nothing happens, or Copilot can't act: check that you're signed in and that "nuget" is ticked in the tools menu.
  • No sparkle action: the warning has to be one of the four audit codes above, and it has to come from a restore.
  • Visual Studio 2022: Learn says it needs manual MCP configuration and version 17.14 or later. That is a separate setup from the built-in Visual Studio 2026 server.

The workflow is review-then-apply, so nothing updates silently. Treat the output like any dependency bump. Check version compatibility and run your tests, because a security fix that breaks your build is still a bad afternoon. The sources don't claim the proposed fixes are guaranteed correct.

Exploring pull requests with the Git agent​

Open Copilot Chat, select the Git agent, and attach a pull request as context from the Git Repository window. You get a summary. Microsoft's description adds that the response includes navigable links that open the relevant comments and files in the IDE's pull request view, and you can ask follow-up questions.

This needs your Git provider's MCP servers connected. GitHub and Azure DevOps are both supported. Microsoft says the agent runs on whichever model you've connected.

The value is saving the hunt through comment threads and changed files. It is not a substitute for reading the diff. A model summary can miss the one comment that matters, so use it as a map and not as an approval.

Also in the release​

Two debugger changes in Microsoft's post have nothing to do with AI:

  • Branch highlighting: while debugging, Visual Studio now uses red and green highlighting on C# if statements with && or || to show which operand decided the result. You can disable it from the editor context menu. Colors are adjustable under Tools > Options > Environment > Fonts and Colors.
  • Podman in Attach to Process: in Debug > Attach to Process, set Connection type to Podman and select Find. Microsoft says .NET and C++ containers both work with no extra configuration.

Stable or Insiders?​

The GitHub changelog tells readers to check the Insiders channel for the latest. Microsoft's blog says this update is in the Stable Channel. Both are consistent. Stable has the September release, and Insiders is where newer work lands. Windows Report describes the release as a Stable Channel update for Community, Professional and Enterprise.

What to do now​

  1. Update Visual Studio 2026 and check that Agent (Preview) appears in Chat.
  2. Re-add Ollama models if you used them.
  3. Enable the nuget MCP server once, so the Error List fixer works.
  4. Connect your Git provider's MCP servers if you want PR exploration.
  5. Decide your policy on BYOM. It is on by default, and the admin controls Microsoft described in August weren't confirmed in this release.

The pattern across all three features is MCP servers plus model choice. That makes the IDE more extensible, and it also means more setup toggles to track across a team.

 

References

  1. GitHub Copilot in Visual Studio — September update GitHub Changelog 2026-10-23T00:17:51+00:00
  2. Unlocking the Power of AI for Every Developer in Visual Studio with Bring your Own Model - Visual Studio Blog devblogs.microsoft.com
  3. Visual Studio September Update Expands BYOM, Adds NuGet Fixes -- Visual Studio Magazine visualstudiomagazine.com