Loading
Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure mode
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill topology-mutation-and-seat-management -a cursor -y
Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.
Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.
rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.
metadata:
cli_surfaces_referenced:
- adopt
- attach
- bind
- discover
- expand
- grow
- launch
- ps
- release
- remove
- shrink
- unclaim
- up
- whoami
openrig:
stage: factory-approved
sibling_skills:
- rig-lifecycle
- seat-scaling-and-specialization
- cross-host-rig-commands
- sidecar-operator
- rig-bundles-and-shareable-artifacts
- specification-system
- extension-and-user-workspaceThe ability to change a rig while it is alive: expand, shrink, launch, remove, discover, bind, adopt, and attach seats or sessions. Seat management includes the stable identifiers, edges, roles, and startup context that make those mutations coherent.
OpenRig should be easy to reach for. A user should be able to add capacity, retire capacity, adopt an existing session, or attach a terminal without rebuilding the whole topology. If mutation is rarely tested, users avoid it and the product collapses back into static launch scripts.
rig grow <rig-id> <member...> for the simple case, a fragment with rig expand or rig add otherwise; see below)rig shrink / rig remove)rig launch)rig bind)rig adopt)rig attach --self)rig grow first, a fragment when you need morerig grow <rig-id> <member...> adds one or more seats to a running rig without
writing YAML. Each seat gets the default agent spec and its default profile.
Check rig grow --help on your installed version; at the time of writing:
--pod <pod>: the target pod; inferred when the rig has one pod--new-pod <pod>: create a new pod for the seats (not together with --pod)--runtime <runtime>: one runtime for every named seat (default claude-code)--cwd <path>: one working directory for every named seat (default: the current directory)--json: output for agentsWrite a fragment instead when a seat needs something rig grow does not set: an
explicit model, a permission policy, a different agent spec or role profile, a
per-seat runtime or working directory, or startup files. Use
rig expand <rig-id> <pod-fragment-path> to add a pod, or
rig add <rig> <pod-namespace> <member-fragment-path> to add one member to an
existing pod (<rig> is the rig id or its exact unique name).
rig up (lifecycle, not mutation)seat-scaling-and-specialization skillseat-continuity-and-handover skillrig whoami doesn't know about it; downstream consumers see partial state.Proof must cover mutation while a rig is active, not just in a clean test fixture. The useful matrix:
| Operation | What to verify |
|---|---|
| Add seat | New seat has queue, startup context, role; rig whoami resolves it |
| Remove seat | Stale references cleaned; edges/permissions updated |
| Adopt existing session | tmux session bound at OpenRig identity layer; rig whoami reports correctly |
| Attach observer terminal | External CLI attachment recorded |
| Verify topology projections after each move | rig ps --nodes reflects current truth, not pre-mutation cache |
A clean-fixture proof is necessary but not sufficient. Live-rig proof catches the failure modes that fixture-mode misses.
Capacity changes must preserve useful roles, routing and durable work. Distinguish
adding or removing a seat from replacing its occupant; use
seat-continuity-and-handover for the latter.
Per cli-reference.md v0.2.0:
rig grow <rig-id> <member...> [--pod <pod> | --new-pod <pod>] [--runtime <runtime>] [--cwd <path>] (added after v0.2.0; check rig grow --help)rig expand <rig-id> <pod-fragment-path> (with optional session_source)rig shrink <rigId> <podRef>rig launch <rig> <nodeRef> (the rig's name or ID)rig remove <rigId> <nodeRef>rig discover [--draft]rig bind <discoveredId> --rig <rigId> (--node <id> | --pod <ns> --member <name>)rig adopt <path> --bind <logicalId=tmuxSessionOrDiscoveryId>rig attach --self --rig <rigId> --node <logicalId>rig unclaim <sessionRef> / rig release <rigId>Select an isolated active rig or an explicitly authorized live target for the relevant operation. Record its running build, before/after topology, continuity and outstanding work. A passing schema check or isolated fixture does not prove an existing live rig was changed correctly. A runtime timeout is indeterminate until its durable and process effects are reconciled; do not retry blindly.
The matrix above is verification guidance, not permission to modify another rig. Name the operation's owner and scope, preserve the state needed for recovery, and retain missing or failed checks in the result. No local experiment or unfinished proof obligation is implied by loading this skill.
openrig-user skill — CLI surface for rig grow / expand / shrink / launch / remove / bind / adopt / attachseat-scaling-and-specialization skill — when to add specialized capacity vs genericseat-continuity-and-handover skill — replacing an occupant on a stable seat (different shape than topology mutation)cross-host-rig-commands skill — cross-host topology mutation (deferred)