Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.259 ·

Task summary field description clarifies source

Task summary docs now spell out that local agents give a model-written progress summary and MCP tasks give the server's status.

Under the hood Internal Changes
JSON All of v2.1.259
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Background TasksArea: what it touches
Internal ChangesKind: in v2.1.259,
Internal ChangesSection of the release

The summary field on task status objects is now documented to clarify its source: for a local_agent task it is a model-generated progress summary, shown only when agentProgressSummaries is enabled, while for a backgrounded mcp_task it is the MCP server's own status message and is always emitted.

Read from
Names in the bundleagentProgressSummaries
What the documentation says
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 agentProgressSummaries, on Agent SDK reference - TypeScript. For a subagent task, the `summary` field carries a model-generated progress summary and is populated only when [`agentProgressSummaries`](#options) is enabled. For a [backgrounded MCP tool call](/docs/en/mcp#automatic-backgrounding-of-long… agent-sdk/typescript see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up agentProgressSummaries, on Agent SDK reference - TypeScript.

See this entry in the whole of v2.1.259 →

Feedback