Roadmap for AI in Visual Studio (October)

Rhea Patel

Product Manager

Today, we’re excited to share our public roadmap, which outlines the next steps in evolving Visual Studio with AI-powered agentic experiences. With every month, we aim to deliver smarter, faster, and more intuitive tools that enhance your coding experience.

Disclaimer: The items outlined here represent ongoing work for the month. They are not commitments or guarantees for delivery within the current month. Upvote the features you or your organization care about most, so we know what to prioritize. With that said, here is what we are working on!

Remote agents

We are starting to bring remote agents like the GitHub Copilot Coding Agent into the platform as a native experience, and this is just the beginning.

Start a GitHub Copilot coding agent session from Chat

New Agents

We’re streamlining how you find and switch between modes and making sure both built-in and extension-provided modes can handle more complex workflows. New agents are in progress:

Agent Mode/Chat:

We’ve been listening to your feedback on Agent Mode and Chat, and we’re making some big improvements.

Tool call improvements

Planning lead development

Planning/To dos in Copilot Chat

Performance

Performance and response quality are the biggest themes we’ve heard in feedback. Improving them is our top priority, and here’s what we’re tackling:

Model Context Protocol (MCP)

We want you to bring your entire development stack into Visual Studio, backed by the same security, governance, and trust you already expect from our product. This sprint, we’re focused on reaching MCP full spec, improving UX and enhancing your governance controls.

Models

We’re committed to giving you access to the latest models, and in Visual Studio we carefully evaluate them to make sure you get the best possible experience. We are continuing to expand even further.

To make Visual Studio a truly AI-integrated IDE, we want to ensure that Copilot is seamlessly available at every step of your development workflow—not just for writing code, but also for searching, fixing errors, writing unit tests, and even committing and pushing your changes.

We’re excited for you to try these new experiences soon. If you have feedback, post it in the developer community ticket linked above. For other ideas or suggestions, drop a comment below or create a new ticket—our team reviews them all.

Thanks 😊

Author

Rhea Patel

Product Manager

5 comments

Discussion is closed. Login to edit/delete existing comments.

Alessio T October 6, 2025

how much “AI” do we need to see movable taskbar again in windows?
- Michael Taylor October 6, 2025
  
  This has absolutely nothing to do with Windows. Perhaps you should post your comments over in a blog that the Windows team, who is responsible for that, actually manages.
David Golub October 4, 2025

I have to say that I'm incredibly frustrated with how Microsoft now seems to be devoting more attention to AI than everything else combined. The fact that a new technology has come into existence does not mean that everything else is suddenly obsolete. Many of us are not particularly keen to be generating our code using a tool that hallucinates API functions that don't actually exist and then spend as much time debugging AI-generated bugs as it would have taken to just write the code ourselves--if not more. Many of us have depended on the excellent developer...
Read more
I have to say that I’m incredibly frustrated with how Microsoft now seems to be devoting more attention to AI than everything else combined. The fact that a new technology has come into existence does not mean that everything else is suddenly obsolete. Many of us are not particularly keen to be generating our code using a tool that hallucinates API functions that don’t actually exist and then spend as much time debugging AI-generated bugs as it would have taken to just write the code ourselves–if not more. Many of us have depended on the excellent developer tools that Microsoft produces, and we’d like to see more of the continual improvement of those tools that we had been seeing before generative AI took the attention away from them.

Read less
- Michael Taylor October 6, 2025
  
  Agreed, if you look at all the VS updates for the last couple of months they boil down to:
  
  - Better integration with Github
  - Using Github Copilot for more stuff
  
  Shockingly, even Azure has taken a backseat. Of course AI being able to do debug diagnostics, writing code, etc are productivity enhancements but still there are some longstanding VS issues that should be addressed unless everyone on the VS team is focused on integrating AI more. Personally I think it is because it is a mandate from MS to bolster their AI numbers and so they can start making money off...
  Read more
  Agreed, if you look at all the VS updates for the last couple of months they boil down to:
  
  – Better integration with Github
  – Using Github Copilot for more stuff
  
  Shockingly, even Azure has taken a backseat. Of course AI being able to do debug diagnostics, writing code, etc are productivity enhancements but still there are some longstanding VS issues that should be addressed unless everyone on the VS team is focused on integrating AI more. Personally I think it is because it is a mandate from MS to bolster their AI numbers and so they can start making money off the very costly investment.
  
  I’d love to be able to start multiple instances of VS without it auto-starting another 10 processes behind the scenes, eating up all my memory and having issues when I’m running more than 2 debugger instances. Maybe the VS team should use their AI debug diagnostics to solve some VS issues. That would make for a great blog article on how a team used AI to solve a real world problem.
  
  Read less
Qing Charles October 3, 2025

Still a lot of bugs in Agent. Good outweighs the bad, but the bugs are annoying.