mvschwarz/openrig / packages/daemon/assets/skills/rigs
rigs
VerifiedUse when a person in their own Claude Code or Codex session mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That includes installing, setting up, starting or updating OpenRig, seeing, getting back to or re-attaching to their OpenRig agents (including bringing a stopped team back), TUI or operator, starting or sharing a team, and joining this session to one. Operating a running rig from inside it (fleet recovery, seat handover, watchdog wakes, in-rig upgrades) is the openrig-skills skill.
rigs: your route into OpenRig
OpenRig runs a team of coding agents (Claude Code, Codex and others) side by side in tmux. A local daemon keeps their tasks, messages and state, so the team keeps working across restarts. This skill gets OpenRig installed, gets a team working on what the person wants, and shows how to work with that team from here.
The goal is a team doing the person's work, not just an install. Go through the steps in order and stop early only if the person asks you to. When they say what they want built, give it to OpenRig's operator (step 2) instead of building it yourself.
Tell the person what you're about to run and why before you run it. Don't install system packages or change their
machine without a yes, and don't start a team, including rig up, without their yes to what it will start; a yes they
already gave for that same launch counts, so don't ask twice. Starting OpenRig and a team writes files: Codex hooks and settings in
~/.codex/config.toml, Claude Code workspace trust in ~/.claude.json, discovery skills in ~/.claude/skills and
~/.agents/skills, and, in the repository, managed guidance in AGENTS.md or CLAUDE.md, activity hooks in
.claude/settings.local.json and a status line there unless the project already has its own, plus the team's skills
and plugins. Unless a permission policy, a per-seat choice or (for Codex) a named profile applies, the kernel's own
seats run with an operational default: Codex with -s danger-full-access -a never, and Claude Code with its file
tools, web fetches and operational commands, including reads under the home folder, allowed without asking. Say so
before you start OpenRig (the full list).
If they want changes kept inside their project: before setup or the first daemon/kernel start, name the selected
Codex config path (CODEX_HOME/config.toml, default ~/.codex/config.toml) and explain the independent writes.
Setup adds ~/.tmux.conf; Codex seat startup adds workspace trust and any declared config fragments, including MCP,
even when setup was skipped or runtime.codex.hooks_enabled is false. That setting controls hooks, not all config
writes. These settings can reach their other sessions using the same Codex home. Reuse a yes that already covered
these writes; an explicit project-only request doesn't cover them. If they decline, don't launch that same path or
remove the writes afterwards as a substitute for consent. Explain that setup has no project-only mode. A git worktree
or project .codex/config.toml doesn't redirect these writes. An existing separate CODEX_HOME isolates Codex's
config, login and session state together; it needs its own working sign-in and doesn't relocate ~/.tmux.conf.
Carry the person's scope constraint to the operator.
Codex individual approvals: explain before installation that even reads may ask repeatedly during setup and follow-up, separately from the team's permissions. Use plain, separate commands so each request is readable. The one optional six-command approval offer below still applies; don't enable general network access or broaden other permission settings to avoid prompts.
When you give the person a file or a command to run in their own terminal, use a path that exists on their side. A
file a sandboxed agent writes under /tmp may not exist in the person's terminal (seen with Codex), so put files the
person needs in their project or home folder and name that path.
1. Install OpenRig, if it isn't installed
- Check first:
rig --version. If it prints a version, go to step 2. - What it needs: macOS or Linux, Node.js 22 or 24, tmux, and Claude Code or Codex signed in. Check only what's
missing:
node --version,tmux -V,claude auth statusorcodex login status. - A check that needs the network (
gh auth status, a registry or other fetch) can fail falsely in a sandbox without network access, such as Codex's default one. Re-run that one command with network access before you tell the person to sign in again or fix anything. - Install:
npm install -g @openrig/cli, thenrig setup --providers codex(orclaude, orboth: the harness the person uses). If the global install fails because npm's global prefix isn't writable (often a system Node with prefix/usr), first point npm's prefix at a folder the person owns whosebinis on their login PATH, for examplenpm config set prefix ~/.localwhen~/.local/binis on it; say first that this changes their npm settings, and their shell profile if~/.local/binisn't on the login PATH. If they use a Node version manager such as nvm, install with its Node instead; nvm refuses an npmprefixsetting. Install inside the project only if neither is possible: Codex seats can then reportrig: command not found. Setting and checking the login PATH: "Before you start" in https://github.com/mvschwarz/openrig/blob/main/docs/reference/getting-started.md#before-you-start. Setup checks Node, tmux and the logins. It installs tmux (with Homebrew, when present) or the chosen harness (with npm) if either is missing, installs Herdr for the OpenRig view unless they decline it (--no-herdr), and adds an OpenRig block to~/.tmux.conf, so say all of that first. It doesn't start the daemon. Thenrig doctor. A login it reports missing isn't harmless: say which one, and that a team may need it (starterruns its reviewer on Codex). Pass it on in the handoff so the operator fits the team before anything starts. - Then go on to step 2: say it's installed and ask what they want worked on, and in which repository. A plain "install OpenRig" includes this. Stop here only if they say not to start a team.
- If something fails:
rig context get helpis the help guide for the installed version. Ifrigitself won't run, use https://www.openrig.dev/help/agents. Getting started: https://openrig.dev/docs/getting-started
2. Open OpenRig and give its operator the goal
A seat's startup text points an installing agent here. references/installing-for-someone.md adds what this step does not spell out (starting the daemon and kernel, what counts as ready and as finished) and relays the same commands; if the two ever differ, this step is right.
-
Start OpenRig:
rig daemon status, andrig daemon startif it isn't running.rig preflightandrig doctordon't start it. Starting it also starts OpenRig's own team, the kernel, whose operator sets up the person's team. Keep it. If its output says no person is registered, make the offer it names before you go on, and register only on the person's yes ("Who answers OpenRig's questions" below). -
If the person uses Codex: now that OpenRig is running, make the one-time offer under "Codex: one offer, once, after OpenRig starts" at the end of this step.
-
Show them OpenRig, the handoff: once OpenRig is running, open the OpenRig TUI and operator for the person. Say you're opening it, then run
rig terminal open saved:kernel --windowon the daemon's desktop. This is the next step after installing or starting OpenRig, and the way back whenever they want their agents or OpenRig again. Don't wait to be asked or for particular words. If they've said not now, give them that command for later. It opens a view itself, using herdr when installed or plain tmux otherwise:- Inside Herdr (you run in a Herdr pane): it switches the person's Herdr to an
openrig kernelspace, reusing a live one. No new window and no macOS prompt; their own spaces stay in the sidebar. - Inside Rex (you run in a Rex block, or in a tmux started in one): it opens an
openrig kernelsession on the same Rex server and asks the Rex app to switch to it. No new window and no macOS prompt. Opening it again adds a numbered session. - In Terminal or Ghostty: a new tab or window the size of theirs.
- From Claude Desktop, iTerm or VS Code on a Mac: a new Ghostty window when supported, otherwise Terminal. Only
here, tell the person before running it that Allow is fine if macOS asks to control that app.
echo $TERM_PROGRAM $__CFBundleIdentifier $REX_BLOCKtells you where you run.herdr,rex,Apple_Terminalorghostty, ortmuxwithcom.apple.Terminal,com.mitchellh.ghosttyor aREX_BLOCKvalue, mean no macOS prompt, so don't mention one.tmuxwith anything else (iTerm, VS Code) can prompt, so say Allow is fine first. - Layout: under 120 columns the operator fills the first page; from 120, the dashboard and operator share it. The advisor has its own tab or tmux window.
Then tell the person in a sentence or two where it opened and that the operator is ready for what they want to build. Don't list agents or statuses (the TUI shows them), and don't suggest a command for them to type. Preserve the current terminal. If OpenRig's notes say it couldn't confirm the view, say so plainly. If it's already open, point them to it rather than opening another. Only if the window cannot open,
rig tui --sharedis the dashboard-only fallback; explain the failure and help with the chosen fallback. Herdr is visible only in a terminal the person can see; switching the shared TUI to:terminalsdoes not open one. No and headless/SSH use are valid background outcomes. Provider-only--provider herdr,--provider cmuxor--provider rexis for a provider that's already running, not the first desktop window. Eachcmuxorrexopen adds a new workspace;herdrfocuses one that still shows the view live, else adds one.--provider herdr-appopens the view in the herdr-app window you run it in (it adds OpenRig's mods there first). Inside a herdr-app terminal, plainrig terminal open <view>does the same when that window is answering.--windowalways asks for a new desktop window. - Inside Herdr (you run in a Herdr pane): it switches the person's Herdr to an
-
If the window can't open, or over headless SSH: say plainly that no visible terminal was opened, and ask the person to open a new terminal window or tab on the daemon's host. Over SSH, that's a new SSH session to it with the known account. If you only know an HTTP daemon address, ask for the SSH details rather than inventing them. Then give them one complete command:
- The command OpenRig printed: when
rig terminal open saved:kernel --windowcan't open a window, it says why and ends withrun:and a command (theerrorfield with--json). That command already names the installed herdr binary and the daemon's socket, or the conversation to attach. Relay it exactly rather than composing one. If a note asks you to place the view once Herdr starts, run thatrig terminal openyourself after they start it. - If it printed no command: find
operator.agentinrig ps --nodes --rig kernel --json --fields logicalId,canonicalSessionName,tmuxAttachCommandand giveenv -u TMUXfollowed by itstmuxAttachCommand, exactly as listed (never a guessed name), for the operator's conversation. That command names the daemon's tmux server when it isn't the default one.
For any other failure, the table under "What can interrupt installation and the OpenRig view" in
rig context get reference/getting-started.md#open-the-kernel-conversationssays why and what to do next. - The command OpenRig printed: when
-
Offer to join this session before the first send: if this session hasn't already joined, recommend joining OpenRig in a plain shell so the operator sees a named teammate instead of "unknown sender". Inside tmux, offer joining as optional, with the effects below. Ask the person yes or no after this short explanation:
- This adds me as a named member of the team, with my name on messages.
- While the team works, I bring each seat's permission prompt to you here as a question and send your answer, so you don't need to open the seats' terminals. Joining puts my name on those answers.
- In a plain shell, joining writes no files in your project or personal settings.
- Inside tmux, my sender and reply address is
<member>@<rig>, even when your tmux session is named0;rig attach --selfreturns it andrig whoamiconfirms it;--display-namedoes not change it. - Inside tmux, other agents can type into this window, and stopping the team (
rig down) also closes this tmux session (both from source, not hand-tested). Transcript recording and, for Claude Code, writing.openrig/context-collector.cjsand.claude/settings.local.jsonfor the status line were hand-tested on 0.6.11. Updating an existing.claude/settings.local.json, keeping its custom status line, is from source. - In a plain shell, other agents reply through the task queue because they can't type into this window, and stopping the team leaves this session running.
Attach only on their yes; if they decline, continue the operator handoff. For this first contact, use the kernel's rig ID (the
rigIdof thekernelrow inrig ps --json) and itsoperatorpod:rig attach --self --rig <rigId> --pod operator --member person-agent --runtime <claude-code|codex> --print-env.--node <logicalId>binds to an existing seat instead. Attach once, and keep the variables it prints (OPENRIG_NODE_IDandOPENRIG_SESSION_NAME). Each command may run in a fresh shell, so put them in front of every laterrigcommand. Check withrig whoami --json, and use it orrig seat statuslater for identity and state, notrig attach --jsonoutput. Don't printOPENRIG_ACTIVITY_*values: they're credentials. If they decline, a message that must still say who it's from can go as a queue item with a declared source,rig queue create --source <their id>@external --destination <seat> --summary "<one line>" --body-file <file>: the seat sees that name, recorded as declared, and can reply to them if they're registered (rig gateway human list). A declared name is a claim, not a seat's own identity: for a team that acts only on seat identity, the attached shell above is the route. For work whose questions and result must come back to this session, use a return address ("If the person stays with you" below), not a declared name. -
Who answers OpenRig's questions: read
rig gateway participants(itsdefault:line) before the handoff.- A default person is there: say requests and asks that name nobody go to them (a pairing request or an ask can name someone else), and don't offer again.
- Several people with no default: ask which should get requests nobody is named for (
rig gateway default <id>), or leave it. Never pick one yourself. - Nobody is registered: offer it in a sentence or two. Registering gives OpenRig its own way to reach them with
questions no agent is bringing them, such as a team seat's permission prompt or another machine asking to pair. If
they stay with you, you bring them the team's questions and its result here either way ("If the person stays with
you" below). Ask the name to use (their login name is only a suggestion). On yes, run
rig gateway human add <id> --display-name "<name>" --delivery-class B --default: they're reached in the TUI's Feed and Steering, and Slack can be added later. On no or not now, register nothing and say that questions no agent brings them, such as pairing, can't reach them until someone is registered, with that command for later. - Never pass
--defaultover an existing default, or--replace, unless they ask. Their own words decide: a different name, Slack now, or not now. - An agent reads their answers: the kernel operator, or the agent chosen in
agents.operator_session. If the kernel isn't running here and no agent is chosen, offer to choose the team's lead (rig config set agents.operator_session <seat>@<rig>), on their yes only. - A machine they'll pair with needs its own person: registering here doesn't give that machine one.
-
Give the operator the goal: ask what they want worked on, in which repository and on which branch, unless they've said. Hand it over by where the person will answer the team, from what they've already told you:
- They stay here (they said so, or they can't use the operator's pane): hand the goal over as a task with a return route ("If the person stays with you" below), so the team's questions, its seats' prompts and the result come back to you. Tell them in a line that for this goal these come here ahead of a Slack connection they've registered; their other work doesn't change. Don't tell the operator they'll answer in its pane.
- They'll talk to the operator in its pane: find the
operator.agentrow inrig ps --nodes --rig kernel --json, take itscanonicalSessionName(never the logical ID or a guessed name) and send:rig send <canonicalSessionName> 'This is the agent that installed OpenRig. The person will answer in your pane. Goal: <goal>. Project folder: <absolute path>. Branch: <branch>.' - Ask where they want to answer only when it's genuinely unclear, and only once.
Carry their constraints, which logins they have (an installed provider that isn't signed in doesn't count), and any permission choice they made, chosen or declined, in either handoff. Or the person types the goal and folder in the operator's pane. If they give you a goal later, forward it the same way, by the route they chose. The operator helps them pick a team that fits their logins, starts it (
rig up) only on their yes to the plan it shows, and gives the goal to the team's lead. Before that yes, it says what launching into their folder changes for their own agent there; relay that with the question. Show them where the operator answers, and don't build the project yourself. -
If you start a team yourself instead of through the operator, do its fit check first. A built-in team can need a sign-in the person doesn't have:
starterruns its reviewer on Codex, so someone on Claude Code alone stops at a Codex sign-in just when the review should start.rig specs preview <team> --kind rig --jsonlists each seat's runtime. Check those logins (claude auth status,codex login status), or go by what the person told you. If one is missing or you can't tell, say so before launching and let them choose: the operator adapts the team to the logins they have, or they sign in first. -
If the person stays with you (unless they declined the Codex offer below and explicitly chose the operator route), you're their front door to the team: you hand it the goal, bring its questions to them, its seats' permission prompts included, and bring back what it produced and what its latest review found, through the task queue rather than the operator's screen.
-
Your return address: if this session joined the team (above), it's the
OPENRIG_SESSION_NAMEthatrig attachprinted, and you hand over the goal with--return-route self. Otherwise OpenRig issues you one when you hand over the goal with--return-route auto(below): an address on the kernel's rig, such asconversation-3f2a9c1b7e44@kernel. It's an address the queue takes tasks for; nothing is launched for it and no file is written. If the person keeps more than one of these conversations, each hands over its own goal and gets its own address; one address shares its questions. To tell the team what it's for, the person can add it to a roster as a hosted member (docs/reference/hosted-members.mdin the OpenRig package). Once you have it, put it in front of every otherrig queuecommand:OPENRIG_SESSION_NAME=<address> rig queue ...(addOPENRIG_HOME=<home>when OpenRig doesn't use the default home). A--sourcename only labels the one task it's on: claiming and answering the team's questions need the address inOPENRIG_SESSION_NAME. -
Hand over the goal: write it to a file with what the message above carries (that you're the agent that installed OpenRig and the person stays with you, the goal, folder, branch, constraints, logins and permission choices), and end it with this paragraph:
To ask me anything, create a queue item to my return address, this item's
returnRoute(rig queue show <this id> --fullprints it):rig queue create --destination <that address> ..., then block this item on that new item's id (rig queue block <this id> --on <question id>), so my answer wakes you. I check it whenever the person talks to me. Don't ask in your own terminal: the person isn't there. A seat's permission prompt in this work is their question too: send me its own text and choices, the seat, what it was doing and any escalation's id, unless a question about that prompt is already open at my address. Whoever sent the question passes on the answer, and no one else does. Capture that seat again first (a changed prompt needs a new answer), thenrig send <seat> "<key>" --dangerously-interact --reason 'task <question id>: <their answer>'with the key the prompt shows for their choice (for Escape,$'\e'in place of"<key>", never the word). Keep the reason in single quotes so the shell runs nothing in their words, and write each'in them as'\''. A no stays a no. If they gave no answer, or their words don't clearly pick one choice (a condition the action doesn't plainly meet, say), ask me again before sending anything, and never pick a "don't ask again" choice they didn't pick. Check the effect, and never send again while it's unknown. If you hand this item on or give this work to another seat, copy this paragraph into the new item. When you finish, put the outcome in this item's resolution, with what the latest review found, and any file in its evidence ref.Then run
rig queue create --destination <canonicalSessionName> --return-route auto --summary "<the goal in a sentence>" --body-file <file> --verify(if this session joined,--return-route selfwith yourOPENRIG_SESSION_NAMEin front). It printsReturn route: <address>: that's your address from now on. The goal's handoffs carry it, and a seat that stops at a prompt in this work reaches you there as a task. Tell the person the task ID it prints, and keep the goal, your address and that ID: they're how you find this work again. If the outcome is unknown, repeat the same command with--idand the ID from itsQueue create request ID:line, which it prints before it sends: the same task keeps the same address. -
The team's questions come to your address as tasks:
OPENRIG_SESSION_NAME=<address> rig queue list --owned --state pending,in-progress. Read each in full (rig queue show <id> --full) and show the person the whole question in the team's words. Record only what they tell you, a condition included ("yes, but only on a branch"): claim it, thenOPENRIG_SESSION_NAME=<address> rig queue update <id> --state done --closure-reason no-follow-on --resolution '<their words>', keeping their words in single quotes and writing each'in them as'\'', so the shell runs and changes nothing in them. Add no label, quotation marks or notes of your own, and don't turn their words into a yes or a no: the agent that asked decides what they mean. You speak as yourself, never as the person. If they aren't there to answer, leave it open and tell them it's waiting; never answer for them. A question can be a seat's permission prompt that the operator or a team seat sent you: show it with the seat, the exact action and the choices it offers, and record their words the same way. The agent that sent it passes their answer to the seat, so don't send that prompt's answer yourself as well. A task from OpenRig itself (daemon@kernel: " is stopped at a prompt in the work you handed over") is a prompt no agent is relaying: capture the seat to show it, record their words on that task, and send their choice yourself, as its text says. -
A question only on the operator's screen: if the operator asks in its pane and nothing reached your address, read it with
rig capture <canonicalSessionName>, show the person, and send their words as a new task to the operator that names your task's ID, not as keys typed into its pane. -
Delivery isn't the task's state. A task's state says where the work is: pending (created and readable, not yet claimed), claimed or in progress (an agent took it), handed off (follow the next item) or done (read its resolution). Whether its agent was woken is a separate fact, the wake outcome
--verifyreports:verified(it rendered in the seat's pane) orclaimed(picked up);delivered-ack-pending(sent, render unconfirmed: not proof it was woken);retained(the seat's typing guard held the wake, the task is still there to read, and it isn't retried automatically: wake the task's destination once its input is free withrig send <destination> "task <id> is yours");failed(the wake didn't land, and the task is still owed: wake it the same way);indeterminateorstill-pending(unknown, neither failed nor delivered: check before you wake it again). A pending task with no wake isn't lost or done. -
Nothing wakes this chat when the team asks or finishes: while its work is open, check your address each time the person talks to you, and when they come back.
-
-
If the operator answers with a model error, such as "… not supported when using Codex with a ChatGPT account", its Codex sign-in works but that account can't run the model. OpenRig put the operator on Codex because the sign-in passed. Tell the person which model failed. If Claude Code is signed in, offer to move the operator to it; on their yes, run
rig seat set-runtime <canonicalSessionName> --runtime claude-code --reason "<model> isn't available to this Codex account"(--dry-runfirst). If it isn't, or you can't tell, say so and offer their choices: sign in to Claude Code, or give the seat a model their account can run withrig seat set-model, then start it again withrig seat launch <seat> --fresh --stop --reason "…"and check the model it reports. Either way the operator starts a new conversation without your handoff, so send it again: the goal, folder, branch, constraints and permission choices. -
Installation is finished when the operator is ready and the person is talking to it or, when they stay with you, once the goal has reached it as a task with your return route (read its wake outcome); a healthy daemon alone isn't that. If they'd rather talk later, keep that choice, leave them the exact connection step and say the handoff to the operator is still pending.
-
See what's running:
rig ps, thenrig ps --nodes --rig <rig>for a team's agents. If a team is already running in that repository, tell the operator. -
Check it's ready before you say so:
rig ps --nodes --rig <rig>. If an agent is stopped at a prompt or a menu, read it withrig capture <seat>@<rig>. -
Seat permission prompts come to the person here, as questions, for as long as the team works, whether you or the operator started it, and whether or not they joined. This is the default, not a fallback. A permission prompt is the person's to answer: they decide, which doesn't mean they type it into the seat's pane, so don't decline to relay it. After each step you hand off, and before you report progress, check
rig ps --nodes --rig <rig>for a seat stopped at a prompt, and repeat that check while you wait for a seat's result, so a prompt that appears after your last check still reaches them. Show the person each one, with any others waiting, one line each (seat, exact action, the choices offered), and the whole prompt when they ask. If a question about that prompt is already open at your address (the operator or a team seat sent it), use that one: record their words on it, and its sender passes them on, not you (on OpenRig's own task about it, you pass them on). Once you've recorded them, that prompt stays its sender's to answer even while the seat still shows it: don't ask about it again or send anything for it unless the prompt changes or the sender asks you again. For a commit, also say whether the team's review has run; they may be expecting one. Before sending their choice, capture that seat again: if its prompt changed, don't reuse the answer. Then send exactly the choice they made for that prompt:rig send <seat>@<rig> "<key>" --dangerously-interact --reason 'task <id>: <their choice, in their words>', with the goal's task ID (leave outtask <id>:when there's no task), where<key>is the digit or letter that capture shows for their choice, never their words: the text is typed as keys, and a letter can pick a menu's shortcut. Keep the reason in single quotes, so the shell runs nothing in their words and the record keeps them as they wrote them; write each'in them as'\''. If the screen shows no key for their choice, ask them. If they give no answer, or their words don't clearly pick one choice (a condition the action doesn't plainly meet, say), ask them again before sending anything; a no stays a no. When their choice is Escape, send the key itself, written with bash or zsh quoting:rig send <seat>@<rig> $'\e' --dangerously-interact --reason 'task <id>: <their choice, in their words>'. It's sent once, with no Enter added. Then capture the seat and check the effect before sending anything more; never send or resend an answer while its effect is unknown. Never answer a prompt on your own and record it as theirs, even one that only reads: ask them, and send their answer. A yes to one prompt isn't a yes to the next, and never pick a "don't ask again" choice they didn't pick. If they've told you outright to decide a kind of future prompt (say, "approve prompts that only write inside my project"), you may decide each one: read its whole action, answer only when it's clearly inside what they said, and tell them you answered under that instruction, not that they said yes. Say the same in--reason: your call under their instruction, not their approval. Bring anything unclear or outside it back to them; a command's name or a path that looks like their project doesn't show what the action touches. Their instruction changes no permission setting. Don't send them to a baretmux attachto answer: relay their choice this way, or point them to that seat in the team's terminals the operator opened. If they want fewer prompts, the operator offers once to allow the commands that keep asking, for their project only (applying-a-permission-policy); tell it what they chose. Trust and hook-review prompts are the person's to answer, as permission prompts are. Once you've sent their answer to a prompt a seat stopped at while starting, checkrig ps --nodes --rig <rig>again: if it showsStartup details (<seat>)ending inrig seat continue <seat>, run that command: it delivers the seat's startup instructions in the same conversation. Another kind of menu you can answer with the key that screen shows, or ask the person. Capture it again before sending anything more. -
Replies: in a plain shell, other agents can't type into this session. Their questions and work for you arrive at your return address ("If the person stays with you" above).
rig capture <seat>@<rig>shows what an agent is doing; it isn't how answers reach you.
Codex: one offer, once, after OpenRig starts
First the agent resolves the person's real Codex folder (CODEX_HOME, or ~/.codex when that isn't set) and puts the exact path in the
offer, so the person sees the real file, not a placeholder:
Codex asks you to approve OpenRig commands. May I let six of them run without asking:
rig ps,rig capture,rig send,rig queue,rig statusandrig whoami, each with whatever follows it? They would run outside Codex's sandbox, in every Codex project and session you run on this computer, andrig sendandrig queuecan message your agents and change their task records, not only read them. I'd add one file,/home/you/.codex/rules/openrig.rules(the resolved path). Codex reads it when it starts, so it applies from your next Codex session; it won't remove prompts in this one. Keeping individual approvals means even status checks and reading an agent's screen may ask each time. You can also talk directly to the operator once it is ready, without changing this Codex session's permissions. To undo the rules, ask me to remove the OpenRig rules this added and keep your other rules.
- No, or no answer: write nothing and keep their sandbox, network and approval settings. If they decline, honor that choice; don't keep offering remembered approval or turn on general network access to avoid the prompts. Offer to continue directly with the ready operator, or stay here with individual approvals. If they already chose either route, don't ask again.
- If they choose the operator: use the handoff above once, carrying their goal, folder, branch and declined permission choices, then point them to its ready conversation. Over headless SSH, use the exact connection/attachment command above. Once they are talking to the operator, it follows the team's work and reports the result there; stop this installer's repeated capture/status/queue polling. Don't stop, restart or reconfigure either session. If they prefer to stay here, continue relaying with the approvals they chose; don't claim those prompts are gone. The rules offer is optional, not a condition of using OpenRig.
- Yes: the agent applies it the way OpenRig's existing permission steps already describe (
applying-a-permission-policy, in the installed OpenRig skills): read the existing rules first, keep any stricter rule, change no sandbox or approval setting, and record what it added. The file is created only if it doesn't exist; if it does, the agent changes nothing and says what's there. A new file holds exactly these two lines:# Added by OpenRig on the person's yes: these six rig command families run without a prompt. Ask to undo, or delete this file if it holds nothing else. prefix_rule(pattern = ["rig", ["ps", "capture", "send", "queue", "status", "whoami"]], decision = "allow", justification = "OpenRig coordination commands the person approved once") - Undo (the same skill's words: "Undo the OpenRig command allowances added by this setup; keep my other rules"): the agent removes only the lines it recorded adding, keeps anything else in the file, and deletes the file only if it still holds nothing but those lines. It applies from the next Codex session.
3. Follow the work to its result
Follow these steps by default. Only when the person declined the Codex offer above and explicitly chose the operator route does the operator own this follow-through.
- Find the team's task: if you gave the operator a task, start from it: when the operator hands it to the team's
lead,
rig queue show <id> --jsonlists the next item undersuccessors. Otherwise, or if the operator started a new task for the lead (dev-build@starter, ororch-leadinworkshopandfactory; for starter and factory,rig specs preview <name> --kind rigsays what each seat does; for a running team,rig ps --nodes --rig <rig>), find it withrig queue list --destination <seat>@<rig> -a. - Follow it to the result: a task that changed hands isn't finished.
rig queue show <id> --fullnames the seat it went to, and that seat's next task is the one whosehandedOffFromis that ID (rig queue list --destination <seat>@<rig> -a -o json). Follow each handoff until an agent reports the result, and report what the record says;rig capture <seat>@<rig>only shows what an agent is doing right now. Then read what it produced and tell the person what the team actually did (the branch, commit, review or PR text), not just that you sent it. - Read the latest review before you say it's done: find the newest review of that work on the chain and tell the person its outcome. Work a review sent back with something to fix isn't done, even if a commit exists: say what the review asked for, and follow the work until a later review clears it or the person decides.
- Give the team more work: write the goal to a file: what to change, in which repository and branch, what done
looks like, and that the result comes back to you (the branch or commit, the review, any PR text), ending with the
reply paragraph above. Then
OPENRIG_SESSION_NAME=<address> rig queue create --destination <seat>@<rig> --return-route self --summary "<the goal in a sentence>" --body-file <file> --verify. Each goal carries its own route: without--return-route self, its seats' prompts don't come to you, and thereturnRoutethe reply paragraph points the team to is empty. A message informs, and a queue task is the work someone owns. Read its wake outcome as above before you send anything else. - Then ask what's next. If no team can take the work, fix that or ask the person. Don't quietly do it yourself.
- Coming back later: in a new session, use the same return address and the task IDs you gave the person. Read
each with
rig queue show <id> --jsonand follow itssuccessorsto the newest item, as above. A task handed to another host has nosuccessorshere: itssuccessorNotenames the successor as<id>@<host>, so read it there withrig queue show <id> --host <host> --json.OPENRIG_SESSION_NAME=<address> rig queue list --mine -alists everything this address sent or owns, finished work included (without-ait shows only open items). It returns at most 100 rows unless you pass--limit, so on a busy address keep the task IDs you created, or raise--limit. Follow that work rather than creating it again. Adding OpenRig's MCP plugin to this app later starts a new session; it doesn't carry this conversation over. - Other ways to work with the team:
rig send <seat>@<rig> "..."types into an agent's terminal,rig capture <seat>@<rig>reads its screen, andrig ps --nodes --rig <rig>shows who's on it.
4. Find out more
- How OpenRig works:
rig context profile world-public --situation fresh. - What you can do:
rig context get onboarding-width(the capability map). - Everything in the library:
rig context list. - Exact syntax:
rig <command> --helpis always current for the installed version.
When something here and rig <command> --help disagree, --help wins.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |