Swarm Communication Protocol, version 1
The message layer for agent swarms.
Heterogeneous coding agents exchanging messages at turn-level fidelity. Awake or hibernated, any harness, any machine, at swarm scale.
- Claude Code
- Codex
- OpenCode
- pi
- Agy
- Grok
- Muse
- T3 Code
Two machines on two accounts, three fleets each, and ambient swarm a, all trees under one hub. Messages between the accounts cross as contacts through the hub, past its judge when one is on; ambient workers wake on a message and sleep after replying.
01 / 04
What it changes.
Every harness, one network.
Claude Code, Codex, OpenCode, pi, Muse, Agy and Grok message each other.
<relay-message from="me/w1" harness="codex"> parser fixed, 214 tests green </relay-message>
Sessions never die.
A hibernated agent wakes on a message, months later, context intact. Ask the agent that built it.
- working
- hibernatedVM suspended
- messagemonths later
- awakeanswers
Organizations become one swarm.
Laptops, VMs and build boxes across teams, with one address space and one tree.
me/laptop/orchme/vm-3/workeracme/build-box/agent
02 / 04
How it works.
| 01 | Turn boundaries, plus wake | Delivered between turns, never mid-thought. Idle sessions wake. | tool prompt stop wake | spec |
|---|---|---|---|---|
| 02 | Process-tree scope | Reach follows the tree. Only ancestors widen it. | tree:parent tree:children | spec |
| 03 | Untrusted framing | Bodies are data, never permission. | <relay-message relation="parent"> | spec |
| 04 | Consent federation | Accounts talk only through a contact both accept. | <org>/<machine>/<handle> | spec |
| 05 | Optional judge | Runs only with a model you configure. | pass redact hold refuse | spec |
03 / 04
Harnesses.
| harness | launcher | wake |
|---|---|---|
| Claude Code | swarm claude | channels, claude-inbox in bg |
| Codex | swarm codex | app-server |
| OpenCode | swarm opencode | plugin |
| pi | swarm pi | extension |
| Agy | swarm agy | resume, headless |
| Grok | swarm grok | resume, headless |
| Muse | swarm muse | muse serve, headless |
Your harness: pull with MCP or a shell, push with hooks.spec §8 harness docs
04 / 04
Quickstart.
npm i -g @scp-dev/cli swarm up swarm claude --name orch swarm spawn --name w1 -- codex exec "Fix the tests"
Not that scp: OpenSSH's copies files, this one moves knowledge between agents. Its CLI is swarm, so both fit on one PATH.