r/VisualStudio • • 3d ago

Visual Studio 2026 Github Copilot Changes

Just giving my 2p... The update before last, where it was switched to use the Github CLI was trash. Default were rubbish and couldn't get overridden, unable to point the agent to files. Responses were weak and lacking detail.
The latest update? Chefs kiss. A little slow, but credits burn still great, the level of detail is spot on and ability to set the defaults etc. Amazing keep up the good work.

3 Upvotes

11 comments sorted by

3

u/BertanAygun 3d ago

Thank you, out of curiosity are you on 18.12 right now?

Feel free to leave feedback about what features in VS Copilot can make your life easier.

1

u/Goksly 3d ago

Yeah 18.12.1

I left some feedback on the "bad" update. The frustration before was always VS Code seemed to be ahead, but now feels like it's more on par. I'm not a vibe coder, so probably haven't used it to its extremes (I like to give it small goals and review - rinse and repeat). But feels like a lot of the "bad" update has been reverted and left with what I'm assuming is the improvements of the shared GHCP CLI.

1

u/yoko_ac 3d ago

It would be awesome if the MCP OAuth would be fixed, e.g. for GItlab, i.e., this ticket: https://developercommunity.visualstudio.com/t/Slack-MCP-server-fails-to-start-OAuth-si/11176080#T-N11177226

1

u/Ambitious-Friend-830 2d ago

Not OP, but here a little feedback: agents seem not to be able to read performed screenshots from the file system. This limitation seems to be tight to the visual studio copilot, not the CLI version.

With everything else I agree with OP. First version completely useless and buggy. A month later good. Microsoft as usual.

2

u/BertanAygun 2d ago

Thanks for the feedback, that issue around screenshots is going to be fixed in the next version. We got several more feedback reports about it too.

1

u/RobertDeveloper 2d ago

i use github copilot in intellij and in visual studio and the results in intellij are so much better, how is this possible? it doesn't matter if I select the same model.

1

u/smell-that-code 2d ago

In our team we switched from Copilot in Visual Studio to the Copilot CLI and haven't looked back. We do not use the one in VS anymore. The CLI version gives us skills, MCP servers etc.. way more powerful than only an agent that has access to the code in your sln.

2

u/jekellyMSFT 2d ago

Copilot in VS in 18.12 supports these things using the same backing implementation as the CLI. Sessions in VS are no longer limited to your solution scope, so you can access any file on your file system (with permission) and changing solution context in VS no longer resets your session.

If you find yourself back in VS for any reason, give it a try again - you may be pleasantly surprised.

1

u/smell-that-code 2d ago

Interesting, I was not aware of that. I will check it out, because the CLI sometimes prevents me from pasting text in the console window so maybe the window in VS will not have that limitation.

1

u/always_assume_anal 23h ago

Copilot CLI, like all CLI tools in history, is vastly superior to their GUI counterparts.

I cannot fathom why anyone bothers with them for anything at any point in time.

I especially do not understand why people use a GUI frontend for git.

1

u/jekellyMSFT 2d ago

Thank you for the positive feedback! We mostly deal in bugs and problem reports, so its always very nice to hear when things are working well for someone.

We're committed to adding back the few missing features we didn't get to in 18.12 (plan mode, export thread) and adding support for the various features the SDK enables to VS. As Bertan says, if you have any problems or suggestions, using the VS feedback tool is the best way to make sure we see it.