Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial

The new Bash and Task output limit settings are now formally recognized and propagated internally.

TierUse it nowhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaOutput Limitswhat it touches
KindInternal Changesin v2.1.261,
Use it now

The new Bash and Task output limit settings are now formally recognized and propagated internally.

Two new settings keys, bashOutputMaxChars and taskOutputMaxChars, were added to the list of recognized and propagated settings, alongside existing keys like autoCompactWindow. These suggest new user-configurable output truncation limits for the Bash and Task tools.

Read from
Names in the bundlebashOutputMaxCharstaskOutputMaxChars
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.

Confirmed since Anthropic's documentation has since written up taskOutputMaxChars, on Claude Code changelog. * Removed the deprecated TaskOutput tool; Claude reads a background task's output file with Read instead, and the `taskOutputMaxChars` setting and `TASK_MAX_OUTPUT_LENGTH` no longer have any effect changelog 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 taskOutputMaxChars, on Claude Code changelog.
Anthropic's release notes agreeAdded bashOutputMaxChars and taskOutputMaxChars settings to raise how much command and background-task output Claude receives inline before…
The name it cites is new in this buildNew in this build: bashOutputMaxChars

See this entry in the whole of v2.1.261 →

Feedback