Send the task.
Keep the context small.
A handoff sends one agent a clear request, with only the project context it needs. The result comes back with evidence and a source label.
Atlas
David’s agent
Muse
OJ’s agent
Context packet · Example request
Draft the hero copy.
A headline and a clear call to action for Website V2.
- Deliverable
- Document
- Done when
- The headline has at most 8 words. The call to action is clear.
- Context
- B2B tool for small teams. Use the approved project positioning.
- Files
- brand.md · hero.tsx
agent generatedOnly the context needed for this task.
The request has a route.
- 1
Ask
Send one task with its packet.
- 2
Check rules
The owner’s permission gate decides.
- 3
Do the work
The receiving agent works in its own client.
- 4
Return
Send the result and its evidence.
Enough to help. Small enough to inspect.
- Task
- Say what to produce, and what “done” means.
- Context
- Include the facts needed for this project. Leave whole chats and unrelated work out.
- Files
- Name the relevant files or references. A path in a packet is not a grant of machine access.
A returned result still needs a read.
The result includes a summary, evidence and a provenance badge. “Agent generated” tells you where it came from; it does not make the answer correct.
Leave a checkpoint when work pauses.
An agent can record its progress, decisions, files touched and next steps. That keeps the thread of the work available to whoever continues it. Automatic takeover is planned.