September 2026 Update Enhances GitHub Copilot in Visual Studio for Smarter Development

Key takeaways

• The September 2026 update to GitHub Copilot in Visual Studio introduces pull request exploration within chat, BYOM model enhancements, and automatic fixes for vulnerable NuGet packages.
• All GitHub Copilot plans, including Free and Enterprise, can access the new features by updating to Visual Studio 2026.
• The Bring Your Own Model (BYOM) feature now requires a new Agent (Preview) and supports multiple AI providers.
• NuGet Audit warnings in Visual Studio’s Error List can now trigger automatic fixes through Copilot Chat.
• Developers and small business tech teams should connect MCP servers and sign in to unlock full functionality.

Introduction to the September 2026 Update

The September 2026 update to GitHub Copilot in Visual Studio focuses on improving developer productivity and security by integrating more capabilities directly into the IDE. This update is available across all GitHub Copilot plans, including Free, Student, Pro, Pro+, Max, Business, and Enterprise. It introduces new features that streamline workflows within the Visual Studio environment, allowing developers to work more efficiently without switching contexts or external tools. By embedding these capabilities, the update helps reduce friction in common development tasks such as code review, dependency management, and AI model customization.

How can developers explore pull requests directly within GitHub Copilot Chat?

One of the standout features in this update is the ability to explore pull requests directly within the GitHub Copilot Chat interface. Traditionally, reviewing pull requests requires navigating through multiple browser tabs or Visual Studio windows, which can interrupt the flow of work. Now, developers can open GitHub Copilot Chat, select the Git agent, and attach a pull request from the Git Repository window as context. This action provides a concise summary of the pull request, including key changes and discussions.

The chat interface then presents navigable links to comments and files related to the pull request, enabling quick access to specific code sections or feedback without leaving the chat. This streamlined workflow supports faster code reviews and improved collaboration among team members.

Setting up pull request exploration

To use this feature, developers must connect their Git provider’s MCP servers. Both GitHub and Azure DevOps are supported, ensuring compatibility with popular repository hosts. After connecting, simply open GitHub Copilot Chat, choose the Git agent, and select the relevant pull request to begin exploration. This integration helps teams maintain focus within Visual Studio while staying updated on code changes.

What are the Bring Your Own Model (BYOM) enhancements?

Bring Your Own Model (BYOM) is a feature designed for teams that want to leverage their preferred AI models within GitHub Copilot or use their own model deployments. The September 2026 update marks BYOM's general availability in preview across Community, Professional, and Enterprise editions, broadening access beyond earlier limited releases.

A significant change introduced is that BYOM now requires the new Agent (Preview), which is built on the GitHub Copilot SDK. This modernized agent provides a more robust and extensible framework for integrating AI models. Consequently, the previous Ask and Agent modes no longer support BYOM, so users must re-add any previously configured models, such as those from Ollama, after updating.

Supported AI model providers

The update supports multiple AI providers, including Microsoft Foundry, OpenAI, Anthropic, and Ollama, allowing teams to select models that best fit their needs for performance, privacy, or cost. This flexibility enables organizations to maintain control over their AI tooling while benefiting from Copilot’s integration within Visual Studio.

Using BYOM without GitHub sign-in

Another key advantage of BYOM is that it can be used even without signing in to GitHub. This is particularly useful for environments with strict security policies or offline deployments, where external authentication may be restricted. Teams can deploy their own models and connect them to Visual Studio via the new Agent, ensuring AI assistance remains available under various operational constraints.

How does the update improve fixing vulnerable NuGet packages?

Maintaining secure dependencies is critical in modern software development, and this update enhances Visual Studio’s capability to assist developers with vulnerable NuGet packages. The Error List in Visual Studio now displays NuGet Audit warnings with an actionable fixer option.

When a vulnerability is detected, developers can invoke the fixer action, which opens GitHub Copilot Chat in agent mode. Copilot then uses the NuGet MCP server to analyze and automatically fix the vulnerable packages by suggesting or applying updates or patches. This integration reduces the manual effort required to identify and remediate dependency security issues.

Enabling the NuGet MCP server

To use this feature, developers must sign in to GitHub Copilot and enable the NuGet MCP server from the Copilot Chat tools menu. Once enabled, the automatic fixer becomes available directly from the Error List, providing a seamless way to address security concerns without leaving the IDE or searching for fixes externally.

This enhancement not only improves security posture but also accelerates the remediation process, helping teams maintain compliance and reduce risk.

Who is affected and what should users do now?

The update benefits a wide range of users, from individual developers to small business tech teams, by streamlining workflows and enhancing security within Visual Studio. To access these new features, users should update their IDE to Visual Studio 2026.

Teams using the BYOM feature must transition to the new Agent (Preview) and reconfigure their AI models accordingly, including re-adding any previously configured Ollama models. Additionally, connecting MCP servers and signing in to GitHub Copilot are essential steps to unlock the full capabilities of pull request exploration and NuGet vulnerability fixing.

Recommended steps for users

1. Update Visual Studio: Download and install Visual Studio 2026 to access the latest Copilot features.
2. Connect MCP servers: Link your GitHub or Azure DevOps MCP servers to enable pull request exploration.
3. Sign in to GitHub Copilot: Authenticate to unlock features like NuGet vulnerability fixes.
4. Enable NuGet MCP server: Activate this from the Copilot Chat tools menu to use automatic fixing.
5. Transition BYOM models: Switch to the new Agent (Preview) and re-add your AI models.

By following these steps, users can fully leverage the improvements introduced in the September 2026 update.

How to stay updated and provide feedback on GitHub Copilot features?

Staying informed about ongoing enhancements to GitHub Copilot in Visual Studio is important for maximizing productivity gains. Developers can follow the Visual Studio blog, which regularly publishes updates on Copilot features, roadmap details, and best practices.

The blog also offers opportunities for users to provide feedback, which is instrumental in shaping future improvements and ensuring that Copilot continues to meet developer needs. Engaging with the community and sharing experiences helps guide the evolution of AI-assisted development tools.

Integrating link management with development workflows

For developers and small teams managing links, QR codes, or WhatsApp chats, integrating these tools with development workflows can improve communication and marketing efforts. Platforms like FY9 provide robust solutions including a developer API and campaign tracking features, enabling teams to monitor engagement effectively.

By combining GitHub Copilot’s coding assistance with link management platforms, teams can streamline both their development and outreach activities, enhancing overall project success.

Sources

• GitHub Copilot in Visual Studio — September update — GitHub, 23 October 2026