[BUG] Calling advisor tool crash or stop the claude code with following API error Unsupported content type: server_tool_use

Open 💬 5 comments Opened May 31, 2026 by RoshanGerard

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?

Symptom: Calling the advisor tool aborts the assistant turn with API error Unsupported content type: server_tool_use.
Context: Claude Code (Opus 4.8, claude-opus-4-8), VS Code extension. Repeatable — failed on every attempt this session.
Likely cause: The transcript forwarded to the advisor backend contains a server_tool_use content block (from a server-side tool) that the advisor request serializer rejects as an unsupported content type. Probably needs the advisor's transcript-forwarding path to filter or translate server_tool_use/web_search-style blocks before re-submitting.
Impact: advisor is unusable whenever the conversation contains a server-tool block.

What Should Happen?

Claude code call advisor and wait for the advisor response to proceed.

Error Messages/Logs

Unsupported content type: server_tool_use

Steps to Reproduce

Make claude code call advisor

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.157

Claude Code Version

2.1.158

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

Claude code call advisor, as soon as call the advisor claude code stops, again ask to proceed or try using advisor then again claude code interupted and stopped so i asked claude code not to call advisor in this current session, then all work perfectly without advisor no crashes or interruptions.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗