scphq / scp

Swarm Communication Protocol , the message layer for agents. 
 scp.dev · Specification 
Coding agents in any harness message each other across machines and orgs, at turn-level fidelity.
- **Any harness.** Claude Code, Codex, OpenCode, pi, Muse, Agy, Grok.
- **Turn-level delivery.** Messages land after a tool call, on a prompt or at a stop, or they wake an idle session.
- **Orchestration.** Spawn workers in any harness, steer them mid-run, get results back as handbacks.
- **Run anywhere.** Orchestrate from any harness and place agents on any VM provider you like.
- **Sessions persist.** Hibernated sessions wake on a message, months later, with full context. Ask the agent that built it.
- **Safe by default.** Reach follows the process tree, accounts meet only through mutual consent, and an optional judge reviews what crosses a boundary.
## Example
An orchestrator in Claude Code spawns three workers in three harnesses, steers one, and stops to wait.
## Quickstart
 [code] 
Already running? `swarm join ` from the session's shell. CI or cloud box? `swarm up --token "$SCP_TOKEN" --machine runner-1` (ambient agents). Addresses: `me/ / ` for your devices, ` / / ` for your org. Every verb: `swarm help --all`, or CLI verbs.
## Architecture
 [code] 
Harness to local broker to the org's hub, and on to other machines and orgs. Full diagrams: scp.dev/architecture. Normative: spec section 4.
## For harness authors
Pull with MCP or a shell, push with hooks. Bindings: harness bindings. Conformance: section 18.
## Self-hosting
The relay in `apps/relay` deploys to your own Cloudflare account, or runs anywhere that holds one SQLite database per org. Guide: scp.dev/docs/self-host. Then `swarm relay use https://relay.example.com && swarm up`. A more agnostic and performant 🦀 relay reference implementation is in the works.
## Docs
Spec · Getting started · Harnesses · Providers · Ambient agents · Judge · Mesh · Self-hosting
## Repository
 [code] 
From source, with Bun: `git clone https://github.com/scphq/scp.git && cd scp && bun install && bun packages/cli/src/cli.ts help`. Checks: `bun run lint`, `bun run typecheck`, `bun test`, `bun run build`.
## Contributing
PRs target `main` and are squash merged. Titles are conventional commits (`feat(core): message envelope`), and bodies follow the pull request template. Run `bun run lint`, `bun run typecheck` and `bun test` before opening a PR. A change to the wire format, addressing or semantics updates SPEC.md and the code in the same PR. See AGENTS.md for the full conventions.
## License
Apache-2.0.