{"version":"2.1.287","anchor":"background-subagent-launch-confirmation-and-hand-over","canonical_anchor":"background-subagent-launch-confirmation-and-hand-over","heading":"Background subagent launches can now require a confirmation step","tier":"internal","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-subagent-launch-confirmation-and-hand-over","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Background subagent launches can now require a confirmation step\n\nStarting a background subagent can now need confirmation and a hand-over, and is cancelled if refused\n\n**Unclear.** It is not clear what performs the confirmation or when that step applies.\n\n**What**\n\nA subagent is a helper that Claude starts to work on part of a task. Starting one in the background can now go through a step where another part of Claude Code confirms the launch and takes the agent over. If that step refuses, the launch is cancelled. Subagents launched this way cannot show permission prompts. Subagents that are copies of the main conversation are now marked as such.\n\n**Why**\n\nThe way background subagents start has changed. One effect you will notice is that some of them can no longer stop to ask you for permission.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}