Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Text-only status messages mid-task silently end the turn and hand control back to the user

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

Fix Action

Fix / Workaround

  • Workaround added to project CLAUDE.md: "Never end a turn with a text-only message mid-task. Chain narration with the next tool call. Only end a turn when the task is complete or genuinely blocked."
  • Happened repeatedly within a single session.

Code Example

Search(_____)
  ⎿  Found 5 files

✻ Churned for 38s

> why did you stop?

● I didn't stop, just pausing to map all call sites before editing. Continuing now.
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?

When Claude emits a text-only message between tool calls (e.g., a short "let me check X" narration), and no tool call follows in the same turn, the turn terminates. Control is returned to the user as if the task were complete, even though Claude intended only a pause. The user must then send a follow-up message ("continue", "why did you stop?") just to resume work that was already in progress.

What Should Happen?

Narrative text between tool calls should not, on its own, end a turn. Either the turn should remain open until Claude explicitly signals completion, or Claude should be trained/instructed to never emit mid-task narration without chaining it to a tool call in the same message. From the user's perspective, pausing for thought should not look identical to finishing the task.

Error Messages/Logs

Search(_____)
  ⎿  Found 5 files

✻ Churned for 38s

> why did you stop?

● I didn't stop, just pausing to map all call sites before editing. Continuing now.

Steps to Reproduce

  1. Give Claude a multi-step task (e.g., rename a record field across several files after verifying usages).
  2. Observe Claude running a Grep or similar discovery tool.
  3. Claude responds with a short text update (e.g., "Found the usages, now editing the files.") without a tool call attached.
  4. The turn ends. The user is forced to type something to resume.
  5. Repeat: even after resuming, the same pattern can recur on the next discovery step UNLESS explicitly told to chain tool use.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.114

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

  • Workaround added to project CLAUDE.md: "Never end a turn with a text-only message mid-task. Chain narration with the next tool call. Only end a turn when the task is complete or genuinely blocked."
  • Happened repeatedly within a single session.

extent analysis

TL;DR

The issue can be mitigated by ensuring that Claude does not end a turn with a text-only message mid-task, instead chaining narration with the next tool call.

Guidance

  • Review the project's CLAUDE.md file for the added workaround and ensure it is being followed to prevent turns from ending prematurely.
  • Verify that the issue is indeed a regression by comparing the behavior in the current version (2.1.114) with the expected behavior in the previous working version.
  • Investigate the Opus Claude Model configuration to see if there are any settings that can be adjusted to prevent text-only messages from ending turns.
  • Test the issue with different types of tasks and tool calls to see if the problem is specific to certain scenarios or if it is a more general issue.

Example

No code snippet is provided as the issue seems to be related to the configuration or behavior of the Claude model rather than a specific code problem.

Notes

The issue seems to be specific to the Opus Claude Model and the Anthropic API, so any solution may need to take into account the specific characteristics of these systems. Additionally, the fact that this is a regression suggests that a previous version of the system did not exhibit this behavior, so comparing the current version with the previous working version may provide clues about the cause of the issue.

Recommendation

Apply the workaround described in the project's CLAUDE.md file, which instructs Claude to never end a turn with a text-only message mid-task and to chain narration with the next tool call. This should prevent the issue from occurring until a more permanent fix can be found.

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…
#api#search optimization#API routing#API middleware#SSR setup

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] Text-only status messages mid-task silently end the turn and hand control back to the user