Features
OpenRig turns the coding agents you already use into a team that keeps working: a lead that delegates, specialists that build, test and review, and questions that come to you. Here's everything it can do.
Start from where you are
I use Claude Code, Codex or Pi.
Give your agent a team, and work with it from the agent you already use.
I run several agents already.
Stop babysitting terminals.
I build tools and integrations.
Bring your agent or app into a team.
72 features
Start a team in minutes
Starter teams
Three ready teams. Start with Workshop: a lead, a builder, QA and a reviewer for ongoing work in your repo. Starter is a builder and a reviewer for one change; Factory runs a bigger team.
The rigs skill
Your agent sets it up. Ask Claude Code or Codex for a team. It installs OpenRig, tells you what it's changing, and hands you to the operator.
The operator
An operator that runs teams for you. OpenRig's own agent recommends a team for your goal, shows you the plan and starts it when you say go. An advisor helps you think it through.
rig upandrig downA whole team with one command.
rig upstarts every agent, each in its own terminal with a name and a role.rig downstops them together.Your own subscriptions
Runs on the logins you already have. Your agents use your own Claude Code and Codex subscriptions. Open source, self-hosted, no OpenRig account.
One-command install
macOS and Linux, or WSL2 on Windows. One Claude Code or Codex account is enough.
Hand off work and keep it moving
The queue (
rig queue)Give a task to an agent and track it. Every task is assigned to one agent and keeps a history that survives a busy agent, a compaction or a restart. Reassign it in one step.
Wakes
Agents wake up when work is due. Set a task aside until a time, another task or an event, and OpenRig wakes its agent when it's ready.
Stuck-work sweep
Stalled work gets noticed. OpenRig spots agents that stopped with work still open, and alerts whoever should act.
Workflows (
rig workflow)Workflows your lead runs. Write down the steps once. Each step opens when the last one closes, and anything overdue goes back to the lead.
Mission lifecycle
Every mission follows your process. Required steps for your project apply to every mission automatically.
Restore
Restarts don't lose your team. Reboot or stop the team, then bring every agent back to the conversation it was in. On Linux, restarting the daemon's systemd service leaves your agents running.
Managed compaction
Long Claude sessions keep their memory. Before an agent's context fills up, it writes notes on what matters, compacts at the next quiet moment and picks up from its notes afterwards. Off by default.
Seat handover
Swap in a fresh agent. When an agent runs out of room, a new one takes its place with a recap of the work.
Exact resume
Resume exactly the right conversation. Pick the Claude Code or Codex conversation you want an agent to continue.
Fork and snapshot
Fork or save a busy agent. Split one agent into two, or save it as an image to start more like it.
rig execHand a task straight to Claude Code or Codex.
rig execsends one task to either agent, lets it work, and brings back its report.Stream intake
Observations become tasks. Anything an agent or tool flags opens a task on its own, so nothing gets lost.
Decision modelsExperimental
Let a model sort incoming work. A decision model can file each new item as a new task, an existing one, or nothing to do.
Proof judges (
rig proof)Done means accepted. Work counts as finished when someone you named accepts it, not when an agent says so.
See what's happening and step in
The TUI
Your whole team on one screen. See every rig, agent and task, and everything waiting on you, in one terminal view your agents can drive too.
Terminal tiles
Watch agents work side by side. Open any team or task as live terminal tiles in Herdr, cmux or Rex.
Follow views
Follow a task as it moves. Watch each agent's terminal appear as the work reaches it, in Herdr, on Linux and, since 0.7.11, macOS.
Live activity
Know who's working. Every agent shows as working, idle or waiting on you.
The Feed
Questions come to you. When an agent needs a decision, it lands in your Feed and the work waits for your answer.
Slack connector
Run your team from Slack. Post a message and it becomes a task. Agents ask with buttons and reply in threads.
Quiet hours
Routine questions wait until you're back; urgent ones still reach you.
People and roles
Bring your teammates. Register the people you work with and choose who gets the final say.
Written policy
Guidance your agents read. Give each group of people a written policy your agents take into account.
rig captureRead any agent's screen. See what an agent is doing without switching terminals.
Transcript search
Search what your agents said. Ask a question across every agent's recent output and the team chat.
Usage limits
See how much is left. Check how close your Claude agents are to their 5-hour and weekly limits, and when they reset, on Claude Pro or Max.
Token usage
Find the busiest agents. Rank agents by token use over any window.
rig doctorDiagnose problems fast. Health checks explain what's wrong without digging through logs.
Use the agents and accounts you have
Mixed harnesses
Claude, Codex and Pi on one team. Run Claude Code, Codex, Pi and Oh My Pi side by side, all messaging each other and sharing one queue.
Runtime switch
Switch an agent between Claude Code and Codex. Change a running agent's harness and it keeps its name, its tasks and its place, though its conversation starts fresh, from a handover.
Account switching (
rig provider switch)An account per agent. Give an agent its own login, and move it to another account when a subscription runs low.
Per-agent models
The right model for each job. Set each agent's model and reasoning effort.
Roles and edges
Roles and who reports to whom. Give each agent a job and decide who hands work to whom.
Live team changes
Grow or shrink a running team. Add agents while the team keeps working, or take them out.
Adopt existing sessions
Bring in agents you already run. Pull existing Claude Code and Codex sessions into a team without restarting them.
ACP and A2A agents
Delegate to outside agents. Hand a task to an ACP agent such as Hermes or OpenClaw, or to an A2A agent.
Connect other agents and apps
MCP server (
rig mcp serve)Claude Desktop can join your team. So can any MCP app: it sees the team, hands out tasks and reads results. We've run it with Claude Desktop.
Hosted membersExperimental
Put a hosted agent on your team. Give Grok or another hosted agent its own seat and inbox.
OpenRig for VS Code and CursorEarly preview
The editor extension: join from your editor, hand off work, see what needs you and review results as diffs.
The openrig pluginNew in 0.7.11
Work with your team from Claude Code or Codex: hand off a task, follow it, answer the team's questions and read the result without leaving your agent. In VS Code, Copilot CLI and Cursor it can hand off work but not claim or answer.
ACP agent (
rig acp serve)New in 0.7.11Use your team from Zed or T3 Code.
rig acp servemakes your team an ACP agent: a prompt becomes a task, you watch each step, and the team's answer comes back as the reply.Relay connectorExperimental, off by default; new in 0.7.11
Bring in your own chat app. The relay connector sends the team's questions and updates to a bridge you run, and takes the replies back. Built by @smota.
MCP tools per role
Tools for every role. Give a role the MCP servers it needs, once, and every agent in that role gets them.
Agent messaging (
rig send)Agents talk to each other. Whichever harness each runs, your agents message each other directly.
Chatrooms and broadcasts
Team chat and broadcasts. Every team has a chatroom, and one message can reach every agent at once.
See every tool and how it connects on the integrations page.
Run across machines
Multiple hosts
Agents on several machines. Pair machines on a trusted private network and reach every agent from one place.
Launch preview
Preview a launch anywhere. See exactly what will start, on this machine or another, before it does.
Services
Start your services with the team. A team can bring up its dev server or database and wait until they're healthy.
Stay in control
Permission postures
Permissions per agent. Choose how much each agent can do without asking. Routine commands run freely; starting and stopping teams still asks.
Codex profiles
Codex settings per agent. Give each Codex agent its own sandbox, approvals or profile.
Permission requests
Permission requests come to you. When a runner agent asks, answer in the Feed or Slack, in your own words if you like; an agent reads it with the question and decides while the runner waits, and you get a note back saying who decides it.
Typing guard
Type in peace. By default, a message that arrives while you're typing joins your text and goes through. Turn on a guard and messages wait until you're done instead.
Terminal policy
Decide who can act on an agent. Limit how far other agents may step into an agent's terminal.
Give agents what they need to know
Project context
Every agent knows your project. Agents that join learn what your project is for, how it works and which skills it uses.
Worlds
A shared picture from day one. Every agent starts from the same understanding of OpenRig and your project.
Context packs
Docs on demand. Agents load exactly the docs they need, down to one section.
Skills delivery
The right skills for each role. Each agent gets the skills its job calls for, kept out of your project's folders.
Seat lessons (
LEARNED.md)Lessons that outlast the agent. What an agent learns stays with its role for the next one.
Rosters
Know who to ask. A list of specialists your agents check before bringing someone in.
Work folders
Plans you can read and commit. Missions and progress live as plain files in the workspace you choose.
Build your own
Harness contract
Add any coding agent. A short preset gets a harness running, and a published contract covers deeper integration.
Conformance checker
Test your integration before you share it with the conformance checker.