{"version":"2.1.289","anchor":"teammate-spawn-records-spawnedwith-agentspawn-hook-gains","canonical_anchor":"teammate-spawn-records-spawnedwith-agentspawn-hook-gains","heading":"Teammate spawning keeps more detail about how each teammate was started","tier":"internal","area":"Teammates","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/teammate-spawn-records-spawnedwith-agentspawn-hook-gains","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Teammate spawning keeps more detail about how each teammate was started\n\nTeammate records gain a field for how they were spawned, and the agent.spawn hook gains an entry for an argument that was not applied\n\n**Unclear.** Nothing shown here reads either new field, so whether they change any behaviour is unknown.\n\n**What**\n\nA teammate is another Claude agent that Claude Code starts to work alongside the main one. Two internal changes affect how teammates are started:\n\n- Each registered teammate now has a `spawnedWith` field.\n\n- The `agent.spawn` hook, which lets plugin code act when an agent is started, gains an entry for an argument that was not applied, and the step that restores its argument is now wrapped in another step.\n\n**Why**\n\nTogether these suggest plugin hooks may be able to change the settings an agent is started with, while Claude Code remembers what was actually applied.\n\n- Area: Teammates\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}