Claude Code v2.1.277 · 18 Sep 2026
TaskOutput tool removed; task output is now read via the Read tool
The TaskOutput tool was removed; background task output is now read through the Read tool, and its max-length setting was retired
You'll notice Tier: how much it should matter to you
3 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
Background Tasks Area: what it touches
Internal Changes Kind: in v2.1.277, 18 Sep 26
Internal Changes Section of the release
Unclear The finding does not say what the different output hosts are or how their limits differ from the previous taskOutputMaxChars setting.
What
The TaskOutput tool has been removed. Its config field's description now says background task output should be read via the Read tool instead.
TaskOutput was dropped from the internal tool set used alongside Read, Glob, Grep, NotebookRead, Skill, AskUserQuestion , TaskCreate , TaskGet , TaskList , TaskUpdate , TaskStop , Agent, and TodoWrite .
The TASK_MAX_OUTPUT_LENGTH environment variable was dropped from the list of recognized/passthrough settings.
The function that computes the maximum characters allowed for task output no longer reads a taskOutputMaxChars setting; it now derives the limit from the current output host/target instead.
Why
This consolidates reading background task output onto the Read tool instead of a separate TaskOutput tool, and moves the output-length limit from a fixed global setting to something derived from where the output is being read.
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt The finding does not say what the different output hosts are or how their limits differ from the previous taskOutputMaxChars setting.
Anthropic's release notes agree Removed the deprecated TaskOutput tool; Claude reads a background task's output file with Read instead, and the taskOutputMaxChars setting…
See this entry in the whole of v2.1.277 →
18 Sep 2026 · 402 entries, this one is #221.
Use it now29 You'll notice126 Nothing to try yet23 Under the hood224
Open the release →
Names in this entry
tool TaskOutput Temporary probes that checked whether old code paths still ran have been deleted; behaviour is unchanged.
tool AskUserQuestion Auto-mode is stricter: text you asked Claude to review can't grant permission on your behalf.
tool TaskCreate Task tools now turn on via the tasks and todo-tools env vars instead of an organization denylist.
tool TaskGet Todo and task tool calls now collapse in the transcript so bookkeeping stops crowding the conversation.
tool TaskList Task tools now turn on via the tasks and todo-tools env vars instead of an organization denylist.
tool TaskUpdate Task tools now turn on via the tasks and todo-tools env vars instead of an organization denylist.
tool TaskStop The TaskOutput tool was pulled from an internal set of tools available to a Claude Code feature
tool TodoWrite Before a usage limit cuts you off, your work can be committed to a hidden git ref with resume notes.
env TASK_MAX_OUTPUT_LENGTH New settings let you control how much Bash and Task output Claude sees before it gets truncated to a file.
setting taskOutputMaxChars Removed in v2.1.277, together with the TaskOutput tool it sized
Anthropic's note
Upstream's own release notes for v2.1.277 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
← Previous · 220 of 402
Artifact publishing now tracks reserved slugs separately from stranded ones
Under the hood Artifact Publish
In v2.1.277 Internal Changes release-page order
Next → · 222 of 402
FileReadTool bookkeeping map write no longer guarded by an empty-string check
Under the hood File Tools