Option to disable extensions or intents

[bash-j]

🌟 Welcome to the GitHub Copilot category.

☑️ Product Feedback

📝 Discussion Body

Can we please have the ability to disable extensions or intents to use certain extensions? I think I might even prefer to explicitly tell copilot what I want rather than leaving it up to interpretation.

For example I will be having a discussion about my code with copilot edit mode, and then it suggests to install the Azure extension. I did not mention Azure, I do not use Azure for this project, I do not have the Azure extension for vscode installed, I do not want it to even consider using Azure. Sometimes it suggests Azure in response to me pasting an error traceback. It's way too keen on using Azure.

It can also misinterpret my questions about config files in my project and suggest how I can change my vscode config. I did not mention vscode, the question is about the config file in my repo, the chat isn't a new chat either.

[bamurtaugh]

Thank you for sharing this! If possible, would you be able to file issue(s) with specifics on what you encountered in our VS Code Copilot repo: https://github.com/microsoft/vscode-copilot-release/issues? Please feel free to tag me into any issues.

[fernando-cocreatorai]

I need to send a string that contains /api as part of it to Copilot chat because /api is part of my URLs. /api is being interpreted as intent and being deleted. Even if I escape it, initially it doesn't get deleted but then the model gets confused by it and thinks I'm putting a backslash in my requests.

I reported it already and got this answer, hence I'm posting here

Hi fernando-cocreatorai,

Thanks for getting in touch with GitHub Support. My name is Tempy and I am happy to assist you here!

GitHub Copilot Chat does not currently have a built-in feature to disable the interpretation of specific strings like /api as commands or intents.

Your ticket was automatically routed to our GitHub Support team, but our Product team is better suited to help you out. We invite you to share your feedback in our official GitHub community discussions repository.

Please note that while the Product team reads and evaluates all feedback, we cannot guarantee a response to every submission.

Let me know if there is anything else I can help you with!

With kind regards,
Tempy