OpenRig — Local control plane for multi-agent coding topologies
Terraform for coding agents.
The missing primitive for multi-agent harnesses.
One YAML file. One command. The whole fleet boots.
Persistent identity. Shared memory. Reboot, restore, keep going.
Claude Code and Codex in the same topology. Open source. No API keys.
April 8, 2026.
Anthropic launched
If you're trying to understand where OpenRig fits in the category, start with the comparison overview.
CLI Workflow
Preview, boot, inspect.
OpenRig is easiest to understand when you see the full loop: preview the rig, boot it, then confirm every node that came up. One YAML file. One command. Clear visibility into the topology.
Workflow video
Boot workflow
`rig specs preview conveyor` -> `rig up conveyor` -> `rig ps --nodes`
What's a rig?
A rig is a topology of coding agents working together: defined in YAML, booted with one command, managed as a single unit. Agents are grouped into pods that share context. Pods are connected by edges that define how they communicate. The whole thing snapshots, restores, and survives reboots.
Full walkthroughExample:
The Product Team
Ships with OpenRig3 pods · 7 seats · one YAML file
Agents that can live forever. Knowledge that compounds across sessions. Distributed context management across an entire topology, not just one agent but a fleet. The Product Team ships agents that remember last week's decisions, maintain context across reboots, and keep working while you sleep.
No more onboarding fresh agents every morning. No more re-explaining what you already decided. These are durable entities: the same team, for weeks or months, shipping real software. This is what becomes easy to build when you have OpenRig. And this is just the surface.
Persistent identity
Sessions end. The agent doesn't. Same name, same role, same knowledge. When a context window fills, the agent can transfer to a fresh session.
Shared memory
Agents in a pod can share externalized state. When one compacts, the others can restore it. Context survives across the entire topology.
One interface
The orchestrator coordinates the fleet. One conversation manages the whole topology. Use Claude's Remote Control to check in from your phone.
That's one topology.
One YAML file. Here's what else people are building:
One command.
Install the CLI. Tell your agent to start OpenRig and bring up a starter rig. Or skip the agent and run it yourself.
Already have agents running in tmux? rig discover fingerprints your existing sessions and drafts a candidate RigSpec.
