[BUG] VS Code extension: "Unsupported content type: server_tool_use" and "Unsupported content type: advisor_tool_result" errors displayed in conversation
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?
Environment
- Claude Code version: 2.1.87
- VS Code extension version: 2.1.87
- OS: macOS Darwin 25.3.0
- Shell: zsh
Description
During conversations that trigger server-side tool calls (specifically the advisor tool), the VS Code extension displays the following errors in the conversation view:
Unsupported content type: server_tool_useUnsupported content type: advisor_tool_result
The tool calls appear to complete successfully on the backend — responses are returned and the conversation continues normally. The errors are display/rendering artifacts in the extension UI.
Additional context
The CLI version and VS Code extension version are in sync (both 2.1.87). The errors do not appear to block functionality — conversations complete successfully.
What Should Happen?
Expected behavior
Unknown or server-side content block types are handled gracefully and not displayed as errors to the user.
Actual behavior
Error messages Unsupported content type: server_tool_use and Unsupported content type: advisor_tool_result are rendered inline in the conversation UI.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce
- Open a project in VS Code with the Claude Code extension
- Start a conversation that triggers an
advisortool call (any sufficiently complex coding task) - Observe the error messages displayed inline in the conversation
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.87
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
7 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This issue did not happen on 2.1.79. Also I'm not using openrouter, just VS Code Plugin for Claude Code
Hitting the same issue here. My setup is a bit different from the OP — I'm running the VS Code extension over Remote-SSH to a Mac Studio (macOS, headless via Tailscale), with the CLI on the remote host. The /advisor command works perfectly in the CLI terminal on the server. Through the VS Code extension panel, I get the same Unsupported content type: server_tool_use / Unsupported content type: advisor_tool_result errors.
Like the OP notes, the advisor call itself appears to succeed — the model gets the advice and continues — but the extension UI chokes on the block types it doesn't recognize. This is purely a rendering issue on the extension side.
For anyone else hitting this: running /advisor through the VS Code integrated terminal (where the CLI renders its own output) works fine as a workaround. It's only the extension's conversation panel that has the problem.
Would be great to see the extension updated to handle these block types, especially since the advisor tool docs (platform.claude.com/docs/en/agents-and-tools/tool-use/advisor-tool) describe server_tool_use and advisor_tool_result as the expected response structure. Seems like the extension's content block parser just needs to learn about them.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue persists, please reopen
This is still a problem!
Problem still exists!