Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.246 ·

Non-interactive runs retry a response that was cut off mid-stream

A cut-off streaming reply in claude -p is now retried automatically, asking the model to resume.

You'll notice New Features
JSON All of v2.1.246
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Headless ModeArea: what it touches
New FeaturesKind: in v2.1.246,
What probably matters to youSection of the release
What

If a streaming reply dies after the model has already produced output (idle timeout, mid-stream server error, dropped connection, laptop sleep), a claude -p run now re-sends the turn with a note telling the model its response was cut off and to resume from where it stopped, up to a fixed number of attempts. Controlled by tengu_truncated_response_recovery, which defaults to on. Interactive sessions are unchanged and still show the partial reply plus the error line.

Details
  • The synthesized API-error message carries a new truncatedAfterOutput flag, set when output had already been yielded and the stop reason was not tool_use.
  • The retry only fires for non-interactive sessions on the main thread, not in subagents or sidechains.
  • The injected meta user message says "Your response above was cut off mid-stream." and asks the model to continue.
  • Each retry is recorded under query_truncated_response_recovery as nudged with an attempt number, or exhausted once the cap is hit, after which the error message is yielded as before.
  • The re-issued turn is tagged transition: { reason: "truncated_response_recovery" }.
Evidence

tengu_truncated_response_recovery

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleclaude -p
Feature flag
tengu_truncated_response_recovery Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.246: on

Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Connect Claude Code to tools via MCP touched a line naming claude -p after this was published. In `claude -p` runs, [Agent SDK](/docs/en/headless) sessions, and [cloud sessions](/docs/en/claude-code-on-the-web), Claude Code can't show that prompt: it loads project-scoped servers without asking. Claude Code also skips the prompt in a… mcp see the edit
Confirmed since Anthropic's documentation has since written up claude -p, on Hooks reference. 4. The calling process runs `claude -p --resume <session-id>` with the same permission host. The same tool call fires `PreToolUse` again. hooks see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude -p, on Hooks reference.
Anthropic's release notes agreeFixed the UI stopping with a render error on the first tool call when a third-party Anthropic-compatible endpoint (ANTHROPIC_BASE_URL)…
The name it cites is new in this buildNew in this build: tengu_truncated_response_recovery

See this entry in the whole of v2.1.246 →

Feedback