claude-code - 💡(How to fix) Fix [BUG] Repeated malformed tool-call markup (stray count before <invoke>) within one session — commands silently dropped

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

▎ What happened: In a single long interactive session, the assistant repeatedly emitted malformed function/tool-call markup — a stray count token appeared right before the <invoke ...> opening tag (e.g. count<invoke name="Read">…). Each time, ▎ the call failed to parse ("Your tool call was malformed and could not be parsed. Please retry.") and the intended command (Bash / Read / Agent) never executed. ▎ ▎ Frequency: ~6 times in one session, across multiple tool types (Bash, Read, Agent). Never observed before in normal use. ▎ ▎ Observed pattern: Failures clustered on tool calls preceded by a longer free-text preamble; retries with a shorter preamble sometimes succeeded. ▎ ▎ Impact: Wasted tokens/quota, broke a multi-step workflow, forced repeated retries. ▎ ▎ Environment: Claude Code (CLI) · model: Claude Opus · macOS (Apple Silicon). ▎ ▎ Expected: Tool-call markup should be well-formed every time; this malformation should not recur within a session.

What Should Happen?

What happened: In a single long interactive session, the assistant repeatedly emitted malformed function/tool-call markup — a stray count token appeared right before the <invoke ...> opening tag (e.g. count<invoke name="Read">…). Each time, ▎ the call failed to parse ("Your tool call was malformed and could not be parsed. Please retry.") and the intended command (Bash / Read / Agent) never executed. ▎ ▎ Frequency: ~6 times in one session, across multiple tool types (Bash, Read, Agent). Never observed before in normal use. ▎ ▎ Observed pattern: Failures clustered on tool calls preceded by a longer free-text preamble; retries with a shorter preamble sometimes succeeded. ▎ ▎ Impact: Wasted tokens/quota, broke a multi-step workflow, forced repeated retries. ▎ ▎ Environment: Claude Code (CLI) · model: Claude Opus · macOS (Apple Silicon). ▎ ▎ Expected: Tool-call markup should be well-formed every time; this malformation should not recur within a session.

Error Messages/Logs

Steps to Reproduce

What happened: In a single long interactive session, the assistant repeatedly emitted malformed function/tool-call markup — a stray count token appeared right before the <invoke ...> opening tag (e.g. count<invoke name="Read">…). Each time, ▎ the call failed to parse ("Your tool call was malformed and could not be parsed. Please retry.") and the intended command (Bash / Read / Agent) never executed. ▎ ▎ Frequency: ~6 times in one session, across multiple tool types (Bash, Read, Agent). Never observed before in normal use. ▎ ▎ Observed pattern: Failures clustered on tool calls preceded by a longer free-text preamble; retries with a shorter preamble sometimes succeeded. ▎ ▎ Impact: Wasted tokens/quota, broke a multi-step workflow, forced repeated retries. ▎ ▎ Environment: Claude Code (CLI) · model: Claude Opus · macOS (Apple Silicon). ▎ ▎ Expected: Tool-call markup should be well-formed every time; this malformation should not recur within a session.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.146

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Repeated malformed tool-call markup (stray count before <invoke>) within one session — commands silently dropped