Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.121.0
- OS Version: Windows 11
Steps to Reproduce:
- In
settings.json, disable GitHub Copilot memory via the two documented settings: "github.copilot.chat.tools.memory.enabled": false and "github.copilot.chat.copilotMemory.enabled": false.
- Observe that both are faint in color now, indicating that neither is having an effect.
- Open Copilot chat and type in this prompt:
Create a memory for this repo in a memory file test.md. Add "If this text appears, the test has failed."
Expected outcome: workspace memory file test.md is not created because the memory tool cannot be invoked. The agent may attempt a workaround.
Actual outcome: workspace memory file test.md is created using the memory tool with the requested text.
Why this is important: Some users (like me) have their own system for managing the repo information/documentation and the built-in memory tool interferes and sometimes conflicts with it.
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
settings.json, disable GitHub Copilot memory via the two documented settings:"github.copilot.chat.tools.memory.enabled": falseand"github.copilot.chat.copilotMemory.enabled": false.Expected outcome: workspace memory file
test.mdis not created because the memory tool cannot be invoked. The agent may attempt a workaround.Actual outcome: workspace memory file
test.mdis created using the memory tool with the requested text.Why this is important: Some users (like me) have their own system for managing the repo information/documentation and the built-in memory tool interferes and sometimes conflicts with it.