Roadmap for AI in Visual Studio (November)

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!

New Agents

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

We are even working on supporting multiple agents at once

Investigate being able to run multiple VS Agents concurrently

Agent Mode/Chat:

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

Memories Improvements in Chat – Developer Community

Tool call improvements

- Dynamic tool calling in Chat
- Summarize thread history to continue in thread

Planning lead development

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

6 comments

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

Sławek Rosiek November 6, 2025

I was trying to use copilot in VS2026 and was disappointed. One in VSCode works much better. I had feeling that one in VSCode is aware about solution or at least project. Applying changes was also easier/more fluent. VS2026 seams to be slower compared to VSCode. That leads that approval of changes appear to late when I already changed something in the code or switched tab. I would like to have a place/list (similar to git changes) where I can go through all changes if I have to confirm each.
- Michael Taylor November 6, 2025
  
  I don't think VSCode is much better. The UX for both toolsets is horrible. If I were colorblind I'd really be struggling. Using "green" for additions and "red" for deletions just adds to an already heavily overused coloring. I'm sure it looks great with the default theme but those of us using different themes (such as one of the many that ship as part of the official theme pack) realize it is really bad. I have a dark editor and the "red" is more of a washed out magenta. It can be hard to see in some cases.
  
  More often than...
  Read more
  I don’t think VSCode is much better. The UX for both toolsets is horrible. If I were colorblind I’d really be struggling. Using “green” for additions and “red” for deletions just adds to an already heavily overused coloring. I’m sure it looks great with the default theme but those of us using different themes (such as one of the many that ship as part of the official theme pack) realize it is really bad. I have a dark editor and the “red” is more of a washed out magenta. It can be hard to see in some cases.
  
  More often than not it is very confusing as to exactly what AI wants to change in an existing code base. There are indicators going every which way with buttons at the end of the line (to accept/undo), keep and undo buttons at the bottom of the editor, same thing in the Chat. It is like every possible place you can look there is an encouragement to accept or undo the changes. Don’t even get me started on when you want to accept only part of the changes.
  
  The updated quick actions with AI isn’t any better. If you change a couple of lines the same way it figures it out and offers to make the same changes on the next set of lines. The problems include that sometimes it takes 5 or more seconds for it to actually make the offer by which point you’ve moved on or it only does it one or two lines at a time. If I’m changing 20 lines in the exact same way it breaks things up by blocks and it might offer to fix one line or the entire block. It is inconsistent and slow.
  
  When it works, it works pretty good, but the UX is slow, confusing and collides with the other tooling that is available. There seems to be a requirement to force AI into every area of VS. I’d prefer if it were in just 1 area to start with and that area actually worked well before putting the sloppy UX everywhere.
  
  Read less
Andreas Saurwein November 6, 2025

“Test Agent” link not working
Matt Sharpe November 5, 2025

Please ensure users who rely on Visual Studio for productive work on a daily basis can continue to disable all “AI” features.
- Jon November 6, 2025
  
  JetBrains Rider is surprisingly good these days, and it’s easy to turn off all that stuff.
  
  After using VS for as long as it has existed, it took me about two days to get comfortable in Rider.
  
  Turning off all the AI junk took a couple seconds.
  
  MS is rapidly losing the thread…
- Richard Deeming November 6, 2025
  
  When they’ve even lost C# “god” Eric Lippert, then something must be wrong!
  
  > Since I’ve started using VS again, ignoring the bad suggestions being constantly made has unfortunately become second nature.
  > When I was in devdiv my team worked hard to make systems that did NOT suggest that I introduce subtle bugs a dozen times an hour.
  
  bsky.app/profile/ericlippert.com/post/3lyv76akqw22f