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.277 ·

Tools now declare whether their calls can run in the background

Every built-in tool now has a backgrounding field (never, self, or detach) controlling whether it can move to the background mid-run

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

Unclear The finding doesn't say what "self" backgrounding means in practice or which tool uses it.

What

Tool definitions now carry a backgrounding field that controls whether a call to that tool can be moved to the background while it's still running, rather than blocking the conversation until it finishes. The possible values are "never", "self", and "detach".

A helper resolves the effective value, applying the default when a tool doesn't specify one.

Why

This gives Claude Code a consistent, explicit way to know which tool calls are safe to move to the background and which must always block, which matters for features that let long-running tool calls detach without disrupting tools that shouldn't be interrupted or backgrounded.

Read from
Names in the bundlebackgrounding
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 Tools reference touched a line naming backgrounding after this was published. Setting [`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1`](/docs/en/env-vars#variables) or running in [bare mode](/docs/en/headless#start-faster-with-bare-mode) disables auto-backgrounding along with the rest of the background task functionality, … tools-reference see the edit
Confirmed since Anthropic's documentation has since written up backgrounding, 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
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding doesn't say what "self" backgrounding means in practice or which tool uses it.
Anthropic's documentation agreesAnthropic's documentation has since written up backgrounding, on Agent SDK reference - TypeScript.

See this entry in the whole of v2.1.277 →

Feedback