Microsoft says “reliability is the priority” for AI in Visual Studio – a reassurance that may raise eyebrows among developers already living with Copilot’s quirks.

Microsoft has been relentlessly shoveling AI assistants into its venerable code wrangler in recent years, but has now stated: “We’re shifting focus to reliability and refinement.”

Sadly, that focus does not extend to dealing with the occasionally clunky and bloated set of tools that have evolved over decades. Instead, Microsoft is focusing on “tightening core workflows, improving agent stability, and building on the MCP foundations we’ve been laying.”

While the company was careful not to commit to delivering anything, it said it was working to keep Copilot rapid as context grows, kicking off early work to integrate the Copilot CLI into Visual Studio Copilot, and taking initial steps toward a dedicated agent for multi-step task planning and execution.

It also said it would handle scenarios where Copilot and IntelliSense trip over each other or where suggestions appear at the same time. “To resolve these conflicts, we will prioritize IntelliSense completions over Copilot suggestions as it’s more predictable and a loved feature.”

IntelliSense first appeared in Visual Basic 5 a full 30 years ago, although the concept of code completion predates it. Where Copilot attempts to generate useful code snippets, IntelliSense focuses on basic code completion.

In 2023, Microsoft announced that IntelliSense in Visual Studio would “steer” GitHub Copilot based on a developer’s selection in IntelliSense’s list.

While Microsoft’s declaration that it will prioritize reliability and IntelliSense completions over Copilot suggestions will be welcomed, there are plenty of facets in the suite that could use attention, but don’t fall under the category of AI features.

This was articulated in a comment on Microsoft’s announcement:

“I know a small percentage of people are interested in AI, but why must all concentration be on shoe-horning it into every products [sic] when there is so much else that needs to be done?

“SDKs are buggy and incomplete (MAUI/WinUI3 etc), yet get absolutely no love whatsoever. Hundreds of genuine problems and/or enhancements remain outstanding for Visual Studio and all M$ is looking at is damned Co-Pilot.”

Surely not. ®