[BUG] Tool-use markup generated as "court" instead of "antml:invoke" (malformed/parse error, tool not executed)

Open 💬 7 comments Opened Jun 8, 2026 by tshirado1

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?

Claude Code repeatedly emitted tool calls starting with the wrong token "court" instead of the correct "antml:invoke", causing "Your tool call was malformed and could not be parsed" and the tool not being executed. It looked frozen until the user typed "再開" (resume), which made Claude rewrite the call.

Frequency: 30+ times in a single long session.
Triggers (observed): long sessions with many tool calls; multiple tools in one message; a tool call placed right after prose.
Symptom: output shows a literal "court" line followed by <invoke name="..."> instead of the proper antml namespaced tag.
Impact: severe drop in efficiency; user had to repeatedly type "再開" or send screenshots.
Request: auto-correct the malformed token, or detect "court"-prefixed tool calls and auto-retry.

What Should Happen?

下記「court」を行い、CLAUDE CODEが止まる。本来、自動で実行してほしい。

Error Messages/Logs

court
<invoke name="Read">
<parameter name="file_path">C:\Users\tetsuya.shirado.claude\projects\C--Users-tetsuya-shirado\memory\MEMORY.md</parameter>
<parameter name="limit">12</parameter>
</invoke>

Steps to Reproduce

毎回プログラム作成時に再現(ファイルの Editやread時)

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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