2 people reported

All time, since Sep 27.

Subagent stuck thinking, no output

“Its next response ran for almost 13 minutes and ended on max_tokens (64,000 output tokens), and the whole response was a single thinking block.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/1317/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Subagent spends max_tokens turns on thinking with no output. Background subagents end turns on max_tokens with only a thinking block, write no file, and the parent session shows nothing.

Is this your bug?

File my report
Where
Subagents
Versions
2.1.280 to 2.1.300
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Subagent transcripts omit final usage5 people
  2. Headless run kills running background subagents yet exits success2 people
  3. Unrequested multi-agent workflows launch and exhaust usage limits without estimate or conf5 people

Original reports2, newest first

  1. Subagent hits max_tokens with nothing but thinking, gets told to resume, and starts over (37 min, no output)#102429
  2. Subagent burns 256k output tokens on thinking across four max_tokens turns, produces nothing, and the stall watchdog never fires#97647

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.