{"version":"2.1.289","anchor":"agent-teammate-spawn-now-runs-through-the-agentspawn-plugin","canonical_anchor":"agent-teammate-spawn-now-runs-through-the-agentspawn-plugin","heading":"Plugin agent-launch hooks now also apply to teammates","tier":"notice","area":"Plugin Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/agent-teammate-spawn-now-runs-through-the-agentspawn-plugin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Plugin agent-launch hooks now also apply to teammates\n\nStarting a named teammate now goes through a plugin's agent-launch hook, which can block, rewrite or retype it\n\n**What**\n\nStarting a named teammate (an agent that works alongside the main session) now goes through a plugin's `agent.spawn` hook, the plugin code that can block, rewrite or change the type of an agent launch. Before, teammates were started directly and skipped it.\n\nWhen a hook rewrites a teammate launch:\n\n- Your permission rules are checked again against the rewritten launch\n\n- The hook cannot change the teammate into an agent type that does not run as a teammate\n\n- Required MCP servers (external tool integrations) are checked again\n\nThe event reported when the teammate starts now includes its agent id and model.\n\n**Why**\n\nA plugin that controls how agents are launched now covers teammates too, and your permission rules still apply to whatever the hook turns the launch into. This only matters when a plugin uses the agent-launch hook.\n\n- Area: Plugin Hooks\n- Names: `agent.spawn`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}