Product
Primitives for orchestrating swarms — with predictable workflows, evidence, and budgets.
How we're different
- Persistent Beads + disposable sessions to fight context rot.
- Role hierarchy that keeps coordination human-comprehensible.
- Verification harness + merge queue, not “ship and pray”.
Core modules
Bead board
Durable task objects with owners, status, evidence, and acceptance criteria.
Role runtime
Named roles with constraints: what they can do, what needs approval, when to escalate.
Queues + hooks
Every role has a queue and a next-hook pointer so work keeps moving.
Seancing
Restart workers safely with a structured handoff: “what happened, what’s stuck, what’s next”.
Refinery merge queue
Stages diffs, resolves conflicts, and lands verified changes in order.
Cost meter
Token + time budgets per bead and per role to prevent runaway spend.
Interface modes
Code-close
Diffs and tests are first-class. Humans review the sharp edges and approve merges.
Code-at-a-distance
More autonomy, but with stricter budgets and heavier verification (screenshots, lint, typecheck, E2E).
Try the console
Spin up roles, create beads, and run a heartbeat loop.