Use when multiple agents/sessions need asynchronous file-based communication across worktrees, branches, or sessions — defines directory layout, letter naming, frontmatter spec, lifecycle (burn/archive/persist), and the canonical letter types (handoff, plan-ready, greenlight, blocker, decisions, milestone-done, broadcast). Apply when designing or running multi-agent orchestration (one orchestrator
Receba novas skills de Design e Frontend toda segunda
1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
Sendbox Protocol
A file-based, lifecycle-managed letter convention for asynchronous coordination between agent sessions. Letters live in version control alongside code, so handoffs survive session reset, branch switch, and worktree isolation. Battle-tested on a 4-day sprint with 11+ agents, 22+ letter types, and 8 sendbox directories.
When to use
Use when:
One orchestrator session coordinates 2+ implementer sessions (separate worktrees or git branches)
An agent must pause and
[Description truncada. Veja o README completo no GitHub.]