Empty response after tool call sequences — frequent, workflow-breaking

Resolved 💬 3 comments Opened Mar 12, 2026 by caldwellcourtneyc Closed Mar 12, 2026

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?

After Claude completes a sequence of tool calls, the final text response is empty. The spinner/working indicator disappears, tool calls are visible and clearly completed, but no summary or text message appears. Asking "what did you do?" or "please continue" in a new message works — Claude responds normally on the second attempt.

I understand this is the known "empty response with stop_reason: end_turn" behavior where Claude interprets the turn as complete after tool results. I'm reporting it because the frequency and impact warrant a fix, not just a workaround.

What Should Happen?

After completing tool call sequences, Claude should always generate a text response summarizing what was done — not silently end the turn.

Steps to Reproduce

  1. Start a Claude Code session (via Claude Desktop on Windows)
  2. Give Claude a task that requires multiple tool calls (3+ file reads, edits, searches, etc.)
  3. Wait for tool calls to complete
  4. Observe: no text response appears, spinner stops, turn appears complete
  5. Send a follow-up message like "what did you do?" — Claude responds normally

Pattern

  • More likely after longer tool call sequences (3+ tool calls)
  • Tends to happen mid-session, not in the first few exchanges
  • Not related to context compaction — happens well before that limit
  • Common scenario: step away during a multi-tool operation, come back to see no spinner and no response, but tool activity clearly completed

Frequency

Most sessions. Multiple times per session during active workflow.

Impact

High friction. Every occurrence requires a follow-up message to get the summary of what was done. In longer sessions this happens repeatedly. The workaround ("send a continuation prompt") is what I'm already doing — requesting this be prioritized as an actual fix.

Claude Model

Opus

Is this a regression?

Not sure — I've experienced this for as long as I've been using Claude Code.

Claude Code Version

2.1.71

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Claude Desktop

Additional Information

Confirmed by Claude Code's own help system as a known issue ("empty response with stop_reason: end_turn" after tool use sequences).

View original on GitHub ↗

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