Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Oversized Bash output is marked as truncated instead of quietly cut

You'll notice
Useful4 Signal2
Bash Tool

Bash output past the 10 MiB cap is now labelled truncated instead of quietly disappearing.

What

When a command's output passes the 10 MiB accumulation cap, the result is now flagged as truncated rather than silently losing the excess, and one more form of buffer-overflow error is recognised as such.

Details
  • The result records stdoutTruncated once the cap is hit.
  • The overflow detector now also matches errors named MaxBufferError, in addition to the existing ERR_CHILD_PROCESS_STDIO_MAXBUFFER and max-buffer checks.
Evidence

stdoutTruncated

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →