Open cglong opened 9 months ago
I'm not sure I understand the use case here? Could you not just avoid making requests to the chat? Completions is a bit different since the requests are automatic
I assume it is also meant also remove all the extra UI that chat adds in various places. There might also be a assumption that Chat makes some predictive background requests without being manually prompted (which it does not).
Aligning enable/disable settings with Copilot does seem a good idea in general; to give developers fine-grained control and make the Copilot-branded settings work as expected.
It is a good idea, to make sure the experience is coherent. @digitarald Do you think a single setting for both code completion and chat, or 2 separate ones ? It might give more control but also get more confusing with 2 switches
@SmallLemur
Two independent enable/disable settings for code completion and chat would be ideal imo
Managing performance is one convenient use case
Crazy that this option is not available.
The Copilot extension has a setting (
github.copilot.enable
) that allows it to be disabled on a per-workspace basis. Copilot Chat doesn't seem to respect this setting and doesn't seem to have any analogues.