{"version":"2.1.290","anchor":"teammate-ambiguity-message-wording","canonical_anchor":"teammate-ambiguity-message-wording","heading":"TaskStop can stop a named background agent by name, and teammate ids are called addresses","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/teammate-ambiguity-message-wording","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### TaskStop can stop a named background agent by name, and teammate ids are called addresses\n\nTaskStop's instructions now say a named background agent can be stopped by name, and the ambiguous-teammate error asks for the full address (name@team)\n\n**What**\n\n`TaskStop` is the tool Claude uses to stop work running in the background. A teammate is another Claude process working in an agent team, and a background agent is a helper Claude starts to work on its own.\n\n- `TaskStop`'s description, the instructions Claude receives about the tool, gains a line: \"To stop a background agent spawned with a name, pass that name as task_id\".\n\n- The teammate line drops the `(\"name@team\")` format hint. It now reads: pass the teammate's agent ID or bare teammate name as task_id. In the prompt captured under this release, the description is 364 characters.\n\n- When a name matches more than one teammate, the error now asks for the \"full address (name@team)\" instead of the \"full agent ID\". The version that also mentions background agents says to use the full address for the teammate or the task ID for the background agent.\n\n**Why**\n\nClaude can now stop a background agent you started with a name by using that name. The error wording now matches how teammates are referred to elsewhere.\n\n- Area: Agent Teams\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}