{"version":"2.1.323","anchor":"teammate-shutdownplan-approval-gated-to-team-lead-via-lead","canonical_anchor":"teammate-shutdownplan-approval-gated-to-team-lead-via-lead","heading":"Only the team lead can now shut down teammates or approve their plans","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/teammate-shutdownplan-approval-gated-to-team-lead-via-lead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Only the team lead can now shut down teammates or approve their plans\n\nTeammates can no longer shut each other down or approve plans; those actions now need a verified request from the team lead\n\n**Unclear.** It is not clear what switches these checks on, or whether they are on by default.\n\n**What**\n\nIn agent teams, one agent acts as the team lead and starts other agents as teammates. Teammates started in tmux (a terminal tool that runs several sessions side by side) now receive a hidden `--lead-verify-key` argument. It carries the time the teammate was launched and a public key used to check that messages really come from the team lead.\n\nWith this in place:\n\n- A shutdown request from anyone but the lead is refused with \"Only the team lead can ask a teammate to shut down\", and nothing is sent.\n\n- A teammate can approve a shutdown only if a matching request came from the lead.\n\n- Approving or rejecting a plan fails when attempted from a teammate.\n\n- Plan approval replies now carry a digest of the plan, a short fingerprint of its contents.\n\n**Why**\n\nA teammate can no longer shut down its peers or approve its own plan. Those decisions stay with the team lead.\n\n- Area: Agent Teams\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}