{"version":"2.1.285","anchor":"headless-subagents-new-callerisheadlesssubagent-routing","canonical_anchor":"headless-subagents-new-callerisheadlesssubagent-routing","heading":"Subagents in headless sessions have a new input to whether they run in background","tier":"notice","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/headless-subagents-new-callerisheadlesssubagent-routing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Subagents in headless sessions have a new input to whether they run in background\n\nThe Agent tool now considers whether it was called by a subagent in a non-interactive session when deciding to run in the background\n\n**Unclear.** The exact conditions and whether nested subagents end up more or less likely to run in the background are not clear.\n\n**What**\n\nA subagent is a separate helper Claude starts with the Agent tool to work on part of a task. The Agent tool decides whether a subagent runs in the background, meaning it works on its own while the main conversation carries on. That decision now also takes into account whether the caller is itself a subagent in a non-interactive session, such as one started with `-p`. When that is the case and a further condition holds, it changes whether the subagent is forced to run in the background.\n\n**Why**\n\nThis may change whether subagents started by other subagents run in the background when you use `-p`.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}