[BUG] VS Code extension webview still renders 'Unsupported content type: server_tool_use' in v2.1.198 (prior reports #40816, #60446 auto-closed without fix)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet (prior reports #40816 and #60446 were auto-closed as stale/not planned, with users still confirming the bug; the stale-bot asked for a new issue)
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment

• VS Code extension: anthropic.claude-code 2.1.198 (win32-x64)
• Standalone CLI: 2.1.153
• OS: Windows 11 Pro 10.0.26200
• VS Code: standard build

Description

The VS Code extension webview renders the literal string

Unsupported content type: server_tool_use

in the conversation view whenever a thread contains server_tool_use content blocks (emitted by server-side tools such as WebSearch/WebFetch). This appears across many threads, both while streaming and when re-rendering history of past sessions.

The tool calls themselves complete successfully and the model acts on their results. Only the UI rendering is broken, so the bug is cosmetic, but it appears in every conversation that used a server-side tool.

Root cause (from inspecting the shipped bundle)

In webview/index.js of extension v2.1.198, the content-block render function has explicit cases for text, tool_use, tool_result, thinking, and fallback, then falls through to a generic branch:

return E("div",{className:sx.unknownContent,children:["Unsupported content type: ",b("code",{children:e.content.type})]})

There is simply no renderer case for server_tool_use (nor for server tool result blocks such as advisor_tool_result reported in #60446), so every such block hits the fallback.

Reproduction

1. In the VS Code extension, run any prompt that triggers a server-side tool (e.g. WebSearch).
2. Watch the conversation panel: the tool invocation renders as Unsupported content type: server_tool_use.
3. Reopen the thread later: the history re-renders the same error line.

Expected: server tool invocations render like other tool calls (or are collapsed/hidden), instead of a raw fallback error string.

Prior reports

• #40816 (v2.1.87, macOS) - closed by stale-bot as not planned; last comments confirm it still persists.
• #60446 (v2.1.143, Windows) - closed by stale-bot as not planned.
• #64158 (open) - related crash when the advisor tool is involved; this report is about the rendering fallback specifically.

The bug is still present in v2.1.198, so neither closure corresponded to a fix.