microsoft / vscode-copilot-release

Feedback on GitHub Copilot Chat UX in Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat
Creative Commons Attribution 4.0 International
301 stars 28 forks source link

Add option to chat without workspace context #1249

Open EwenDC opened 2 months ago

EwenDC commented 2 months ago

Having a back-and-forth with Copilot is very frustrating due to the lengthly process to collect workspace information (exacerbated by VSCode forcing the "@workspace" context, and the trigger-happiness of the algorithm that determines what to collect). This creates a ~5 second delay before each response that slows down conversation unnecessarily when asking general questions not related to your codebase.

On top of that, it makes Copilot dumber as it unnecessarily prioritises the data it gets from the workspace context over the current chat context. As an example, I was asking Copilot to write a comparator function for sorting arrays in JavaScript. When it responded with a function that only sorted numbers, I asked it to rewrite the function to cover all data types. Rather than pay attention to our chat context, it assumed I must be talking about a random function in a file I had open and started trying to rewrite it. After I restated the prompt about creating a new sorting function, it just parroted back the sorting function in our codebase that I was trying to compare against a Copilot generated implementation.

lramos15 commented 1 month ago

It should not be including workspace everytime. Can you include a screen recording. https://gifcap.dev/ is a tool I use to capture screen recordings

EwenDC commented 1 month ago

Here's me opening a brand new VSCode window, and typing a message without any context. As you can see, the second the message is sent, it gains the @workspace context, and Copilot attempts to scan my workspace. https://github.com/microsoft/vscode-copilot-release/assets/39972488/95d1d023-7739-4358-a6d9-115fbbe79c1d

lramos15 commented 1 month ago

Hi @EwenDC, sorry this got buried a bit in my inbox. On the latest version are you still experiencing this problem?