Description
Does this issue occur when all extensions are disabled?: YES
I’ve tested the new Chat Mode feature, and it currently cannot function like Agent Mode. Despite checking and confirming that all tools (e.g., file creation, terminal execution, tool calling) are available and enabled, the new chat mode is unable to:
• Create files
• Execute terminal code
• Call or use built-in tools (e.g., Python, image generation, web access, etc.)
I’ve retried multiple times and verified the settings, but the issue persists.
Steps to Reproduce:
1. Switch to the new Chat Mode
2. Check that all tools are enabled
3. Attempt to create a file or run terminal code
Expected Behavior:
Chat Mode should behave like Agent Mode and be able to use built-in tools when enabled.
Actual Behavior:
Chat Mode fails to perform any actions involving tools – it neither creates files nor executes any code or tool-based operations.
- VS Code Version: Latest
- OS Version: Win 11 26100.4349
Activity
Chiruu191 commentedon Jun 12, 2025
@isidorn
it says disabled even though its configured in the chat mode instructions.
4regab commentedon Jun 13, 2025
any update? I have the same issue.
aeschli commentedon Jun 13, 2025
Hm, you are correct, I can reproduce.
run
/list test
create_file
tool is not part of the listaeschli commentedon Jun 13, 2025
@roblourens FYI, maybe a recovery candidate
SlalomJustin commentedon Jun 13, 2025
I have this same issue, and found that it occurs only when running local custom prompts in .github/prompts. When opening a new chat window and simply asking the agent to use tools, it does so as expected. When trying to run a custom prompt from a file, it does not.
a-h-abid commentedon Jun 14, 2025
I also tried using below contents. Generated markdown contents shows in the chat, but the file not generates. I've to create it manually, or I switch to Agent mode then have to tell it to generate the file.
edk208 commentedon Jun 14, 2025
I had this problem too. After some digging I found that "editFiles" is not the correct tool name, it is "insertEdit". Then it works as expected.
a-h-abid commentedon Jun 14, 2025
You are right. This worked. Thank you.
4regab commentedon Jun 15, 2025
That worked, @edk208 However, I encountered another issue: it makes some MCPs unable to work.
8 remaining items
charris-msft commentedon Jun 17, 2025
Did you specifically add the tools from the BrowserMCP to your chat mode?
4regab commentedon Jun 17, 2025
I initially enabled all tools and configured the following permissions: 'editFiles', 'createFiles', 'insertEdit', 'runInTerminal', 'getTerminalOutput', 'getTerminalSelection', and 'getTerminalLastCommand'. However, the agent didn’t function as expected.
I managed to get it working by creating a new chat mode agent in a new chat and enabling all tools without modifying the configuration. This worked temporarily, but after some time, the agent stopped being able to use those tools again.
To make it work again, I have to restart VS Code, but even that only works intermittently. The issue seems to persist regardless of configuration changes or restarts.
AdamRidleyAW commentedon Jun 19, 2025
Same issue here, @edk208's comment helped. It seems the Configure Tools option isn't working properly!
janaka commentedon Jun 20, 2025
Yep same issue. Doesn't look like they are very interested.
Reported here also.
microsoft/vscode-copilot-release#12647
Handle toolsets correctly in custom chat modes
Handle toolsets correctly in custom chat modes (#252114)