{"version":"2.1.277","anchor":"new-tool-backgrounding-field-controls-detachselfnever-ex","canonical_anchor":"new-tool-backgrounding-field-controls-detachselfnever-ex","heading":"New tool backgrounding field controls detach\/self\/never execution mode","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-tool-backgrounding-field-controls-detachselfnever-ex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New tool `backgrounding` field controls detach\/self\/never execution mode\n\nTools gain a `backgrounding` setting controlling whether they can keep running in the background\n\n**Unclear.** The finding does not say which tools are actually marked as detach-capable versus self or never, or when background results become visible to the user.\n\n**What**\n\nMany built-in tools \u2014 including `WebFetch`, `WebSearch`, `Bash`, `Task`, `PowerShell`, MCP (Model Context Protocol) tools, and various read-only lookup tools \u2014 now carry a `backgrounding` property set to one of three values: `\"detach\"`, `\"self\"`, or `\"never\"`. Tools without a value default to `\"never\"`. A new internal check looks at whether a tool's `backgrounding` is `\"detach\"` to decide if that tool call is allowed to keep running in the background, with its result delivered later through a separate message once it finishes.\n\n**Why**\n\nThis lays the groundwork for certain tools to run in the background instead of blocking the conversation while they complete, letting Claude Code (and the user) continue working while a long-running tool call finishes elsewhere.\n\n- Area: Background Tasks\n- Names: `backgrounding`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}