That's on Microsoft for their choice of naming/branding.

Absolutely. They've made the same mess with "Copilot" as with ".NET" in the early 00's [0]. Everything was ".NET" from consumer oriented services (".NET Passport"), to "Visual Studio .NET" without anyone understanding what ".NET" was.

Now it's "Microsoft Copilot" which is different from "Microsoft 365 Copilot", which is different from "Copilot Chat" and from "GitHub Copilot", and the many other flavors.

It's a mess.

Still, their developer-focused offering seems to be "GitHub Copilot", which among other things includes "GitHub Copilot CLI" [1], their terminal-based agent. It's not bad.

[0]: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy

[1]: https://github.com/features/copilot/cli/

I've been a C# developer on and off since the dotnet core/standard split. I still have no clue what .NET was ever supposed to mean.

In the context of knowledge workers, It is really about Claude Cowork against Microsoft Copilot suite for all their applications, which is what the OP is referencing ?

Github Copilot can use Claude APIs and has its own problems and challenges.

Microsoft AI performance is primarily not being affected by Github - while significant is much much smaller part of the enterprise revenue stream and their DAU compared to their Office suite apps.

Same for their PR exposure. It is lot more likely to here about Copilot in the office context than Github outside of small niche's like this forum.

Office is now the "Microsoft 365 Copilot App." It's ridiculous.