Andrew

@ChairmanMeow the interface for copilot is “you ask it to do a thing in plain language and it (sometimes) does it”, I’m sure joe shmoe is more than capable of handling that

@ChairmanMeow ok, but again,

1. There is no reason to ask copilot to do this relatively simple task if you have the docs open in front of you

2. If you have to look up instructions for how to prompt copilot to do something then there is no reason for copilot to exist

Just give me one realistic scenario where this information helps someone other than Microsoft’s KPI tracking executives

@ChairmanMeow Sure, but in this scenario you already have the relevant page of documentation open in front of you, so why would you *want* to know that Copilot exists?

@ChairmanMeow if you’re using copilot, why are you reading the docs?

@ChairmanMeow that doesn’t strike me as a particularly strong argument for directing those users to a system that will sometimes just make stuff up?

@ChairmanMeow I think it’s relevant, though — like, if we accept that the whole premise of Copilot is that it doesn’t need to be documented, then you have to ask what Microsoft *were* intending to accomplish by putting it in the docs. Clearly they had *some* goal in mind and “to make people use Copilot” is the only thing I can think it could be. And if this bit of the docs exists not to help the user but to drive traffic to Copilot and that’s, I mean, yeah, that’s an advert disguised as a help file and it’s… at best icky

@ChairmanMeow @abbadon420 isn’t the whole point of copilot that you *don’t* need docs to use it, though? If you’re reading the docs anyway, why wouldn’t you just read how to do it yourself?