{"version":"2.1.302","anchor":"agent-tool-schema-text-subagents-forced-into-background-by","canonical_anchor":"agent-tool-schema-text-subagents-forced-into-background-by","heading":"Background subagent wording now names the terminal, desktop app and VS Code","tier":"internal","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/agent-tool-schema-text-subagents-forced-into-background-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Background subagent wording now names the terminal, desktop app and VS Code\n\nClaude Code's text now says the run-in-background option is withheld when subagents are forced into the background, including with `CLAUDE_CODE_FORK_SUBAGENT=1`\n\n**What**\n\nA subagent is a helper agent that Claude starts to handle part of a task. Claude can normally choose to run one in the background with a `run_in_background` option. Claude Code's internal description of when that option is not offered has been reworded. It now says the option is not offered when subagents are forced into the background, which happens:\n\n- in a terminal\n\n- in the desktop app\n\n- in the VS Code extension\n\n- with `CLAUDE_CODE_FORK_SUBAGENT=1`\n\nThe old wording said only \"the fork gate on\".\n\n**Why**\n\nIt spells out that with fork mode, subagents run in the background, so Claude does not get to choose whether to wait for them.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}