Describe the bug
GitHub Copilot CLI ignores MCP tools/list_changed notifications from MCP servers like Wassette (microsoft/wassette) (see upstream issue at microsoft/wassette#308), so tools added via load-component do not appear until the CLI is restarted.
Internal terminal testing shows the CLI never refreshes its tool list, unlike GitHub Copilot in VS Code which updates immediately.
Repro video (1m48s):
https://www.youtube.com/watch?v=8tQ1TON50IQ
Affected version
0.0.330 Commit: a8bfefe
Steps to reproduce the behavior
- Add an MCP server to Copilot CLI.
- Have it dynamically load a new tool (such as
load-component in Wassette).
- Attempt to invoke the loaded tool. It will fail.
- Reopen Copilot.
- Attempt to invoke the tool. It will succeed.
Expected behavior
Copilot CLI should respond to tools/list_changed and refresh the tool list when new tools are loaded. See VS Code walkthrough at: https://aka.ms/hello-wassette-youtube
Additional context
No response
Describe the bug
GitHub Copilot CLI ignores MCP
tools/list_changednotifications from MCP servers like Wassette (microsoft/wassette) (see upstream issue at microsoft/wassette#308), so tools added viaload-componentdo not appear until the CLI is restarted.Internal terminal testing shows the CLI never refreshes its tool list, unlike GitHub Copilot in VS Code which updates immediately.
Repro video (1m48s):
https://www.youtube.com/watch?v=8tQ1TON50IQ
Affected version
0.0.330 Commit: a8bfefe
Steps to reproduce the behavior
load-componentin Wassette).Expected behavior
Copilot CLI should respond to
tools/list_changedand refresh the tool list when new tools are loaded. See VS Code walkthrough at: https://aka.ms/hello-wassette-youtubeAdditional context
No response