Unclear It is not clear what switches these checks on, or whether they are on by default.
What
In 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.
With this in place:
- 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.
- A teammate can approve a shutdown only if a matching request came from the lead.
- Approving or rejecting a plan fails when attempted from a teammate.
- Plan approval replies now carry a digest of the plan, a short fingerprint of its contents.
Why
A teammate can no longer shut down its peers or approve its own plan. Those decisions stay with the team lead.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear what switches these checks on, or whether they are on by default.