> lack of real integration is basically the core design of most Copilot products
I would wager a month's wages that this is the doing of some internal Security Review, wherein a bunch of out-of-touchers decided that the customers will want to prefer to be Safe and Secure instead of getting some actual value from integrating copilot into shell workflows.
Meanwhile people are yolo'ing it with various janky DIY wires and duct-tape githobbits that mash together whatever open weights model and user-level access to the system (or worse).
> a bunch of out-of-touchers decided that the customers will want to prefer to be Safe
You mean the other way around, right? Because what could possibly go wrong when we let a language model hallucinate its way through which terminal command rhymes best with your prompt according to that SO comment from training data.
i mentioned this upthread but an LLM with enough access to be fully integrated into all apps/services/files in an enterprise managed workstation sounds like privilege escalation attacks just waiting to happen.
You'd be hearing a few more hair raising failure stories if they hadn't done that. And possibly a few big customers institute Win11 or Copilot site wide bans. Or just straight up going out of business. In businesses other than software, it's possible to be legally liable for mistakes.
I would wager a month's wages that this is the doing of some internal Security Review, wherein a bunch of out-of-touchers decided that the customers will want to prefer to be Safe and Secure instead of getting some actual value from integrating copilot into shell workflows.
Meanwhile people are yolo'ing it with various janky DIY wires and duct-tape githobbits that mash together whatever open weights model and user-level access to the system (or worse).