OpenRigv0.6.10

Common workflows

Short sequences for everyday tasks. Read the conditions before running them.

OpenRig cheatsheet

Commands for launching teams, assigning work and picking up where you left off.

151 examples · 14 categories · Verified against 0.6.10 / 3001cc43
Updated for 0.6.10 · Changes since 0.6.5
  • Teams: starter replaces first-project and uses Claude Code build + Codex review. factory has seven seats; workshop installs from its external GitHub bundle.
  • Setup: --providers chooses codex, claude or both. Herdr is installed by default; --no-herdr declines it. Doctor still checks both harnesses.
  • Restore: --existing restores managed guidance. A partial restore is reported with exit 1. Use --fresh for selected logical seats only when choosing a continuity change.
  • Delivery: queue writes return after saving; --verify inspects wake/claim observations. An indeterminate receipt can coexist with a claim. Check before retrying.
  • Capture: --lines N now means the last N lines total; --history-plus-pane retains the old window.
  • Permissions: eligible team and kernel seats now have different launch defaults. Inspect your policy and seat status before launching.
  • Shutdown: down already attempts a recovery snapshot; --snapshot is redundant. Upgrade the CLI and restart the daemon together.

For limits, missing sessions and upgrades, use the workflows above. Read the release notes.

Customize examples my-project / dev-owner

Command reference

Browse by category or search. Scroll inside the list to explore commands.

Version & sources

Checked against release notes and command registrations in OpenRig 0.6.10 / 3001cc43. This is a source-checked reference, not an end-to-end provider test or an exhaustive list of flags. Use rig --help for your installed version.

Set ID variables from actual CLI output: $RIG_ID is a rig ID; $SEAT_ID is a logical seat ID such as dev.owner; $QITEM_ID and $SNAPSHOT_ID identify saved records. Set $BUNDLE_SOURCE to a real bundle path or GitHub folder URL and $ACCOUNT_REF from provider status. Choose rig and seat names that match your team; model availability depends on the harness and account.