[BUG] Claude stops responding mid-task after successful tool calls

Resolved 💬 8 comments Opened Mar 18, 2026 by cspinks-certinia Closed Jun 10, 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?

During a multi-step code editing task (~7 sequential Edit tool calls), Claude stopped responding after the final edit completed successfully. No error, no blocker, no context limit — it simply produced no further output. The user had to manually prompt ("you have stopped") to get Claude to continue.

Environment: Claude Code VSCode extension, claude-opus-4-6, conversation resumed after context compaction.

What Should Happen?

Expected: Claude continues with a summary/next steps after the last tool result.
Actual: Silent stop. User must nudge to resume.

Error Messages/Logs

Steps to Reproduce

I can't provide reliable reproduction steps. The behavior was non-deterministic. I don't know whether it was caused by context compaction, the number of sequential tool calls, the conversation length, or something else entirely.

The conditions under which it transpired were:

  • Conversation had been resumed after context compaction (the session continuation summary was loaded at the start)
  • ~7 sequential Edit tool calls with interleaved Read/Grep calls
  • The last Edit call that succeeded before the stall had a hook warning (Unused public method) but no blocking error
  • Two files were being edited in alternation
  • Model: claude-opus-4-6, VSCode extension

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.54

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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