[BUG] MCP server tools unavailable after /clear in VS Code extension
Resolved 💬 6 comments Opened May 7, 2026 by dylanophir-toast Closed May 8, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
After running /clear in the VS Code extension, MCP server tools (plugins, custom servers) stop being discoverable. Sub-agents spawned after /clear report "0 tool uses" and cannot invoke any MCP tools. ToolSearch calls for MCP tool names return nothing. The session must be fully restarted (new session, not /clear) to restore MCP tool availability.
What Should Happen?
/clear should reset conversation context without dropping the MCP tool registry. MCP tools should remain available and callable after clearing the conversation.
Error Messages/Logs
No explicit error — tools silently become undiscoverable. Sub-agents report completing with "0 tool uses" and the main agent notes "The sudocode MCP tools aren't surfacing through ToolSearch."
Steps to Reproduce
- Open Claude Code in the VS Code extension with one or more MCP servers configured (e.g. a plugin server)
- Confirm MCP tools work — invoke any MCP tool successfully
- Run
/clear - Attempt to use the same MCP tools (directly or via sub-agents)
- Observe: tools are not found, sub-agents complete with 0 tool uses, ToolSearch returns no matches for MCP tool names
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.132
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗