{"version":"2.1.178","anchor":"named-teammate-agent-swarms-teamcreate-teamdelete-removed","canonical_anchor":"named-teammate-agent-swarms-teamcreate-teamdelete-removed","heading":"Named-Teammate Agent Swarms (TeamCreate\/TeamDelete Removed)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/named-teammate-agent-swarms-teamcreate-teamdelete-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### Named-Teammate Agent Swarms (TeamCreate\/TeamDelete Removed)\n\nThe explicit `TeamCreate` and `TeamDelete` tools have been removed. Multi-agent coordination is now done entirely through the `Agent` tool's `name` parameter \u2014 no separate team-creation step is needed.\n\nBefore (v2.1.177):\n\n`\/\/ 1. Call TeamCreate to set up the team \/\/ 2. Call Agent with team_name + name to spawn a teammate \/\/ 3. Call TeamDelete when done` After (v2.1.178):\n\n`\/\/ Just call Agent with a name parameter Agent({ name: \"researcher\", prompt: \"...\" })` **Details** - Agent swarms remain gated by the same feature flag as before - The `team_name` field in `TeammateIdle` hook events is now deprecated (marked `@deprecated`) \u2014 sessions have a single implicit team; the field will be removed in a future release - System prompt guidance now reads: \"If this plan can be broken down into multiple independent tasks, consider spawning named teammates with the Agent tool (pass a `name`) to parallelize the work.\" - \"main\" is now a reserved recipient name for SendMessage \u2014 it routes a message directly to the main conversation **Evidence** Removal of TeamCreate\/TeamDelete tools (search for `\"TeamCreate\"` absent from new file; guidance string search for `\"spawning named teammates with the\"`; reserved name message search for `\"SendMessage routes it to the main conversation\"`)"}