Skip to content

OpenRig 0.7.20

Latest

Choose a tag to compare

@mvschwarz mvschwarz released this 20 Nov 11:42
· 83 commits to main since this release

OpenRig 0.7.20 tells a person's own agent the consent rules first and where a handed-over task's result is, holds automatic delivery while a seat's tmux server is gone, and, when a parked row's wake is refused at a Claude seat's usage limit, retries it at the stated reset. It also lets a workflow instance stay on one pod, adds an opt-in Claude status-line throttle, and fixes a run of smaller CLI, TUI, scope and workflow problems.

Before you upgrade

Run the upgrade in the environment that owns your daemon, keeping the same OPENRIG_HOME (legacy RIGGED_HOME) if you set it. Stop the daemon, back up its database, install the patch, then restart it. Your agents keep running; do not use rig down for this upgrade.

If the daemon was started with --db, or with OPENRIG_DB (legacy RIGGED_DB) set differently from this shell, replace the DB= line below with that actual database path. Pass the same --db "$DB" to every rig daemon start, including recovery; rig config get db.path reads this shell's configuration, not the running daemon's launch arguments or environment.

DB="$(rig config get db.path)" &&
STOP="$(rig daemon stop)" && printf '%s\n' "$STOP" &&
{ printf '%s\n' "$STOP" | grep -qx 'Daemon stopped' || { echo "The stop wasn't confirmed clean; see below before continuing." >&2; false; }; } &&
BACKUP="$DB.before-0.7.20-$(date -u +%Y%m%dT%H%M%SZ)" &&
{ [ ! -e "$BACKUP" ] || { echo "$BACKUP already exists; keep it and run again." >&2; false; }; } &&
cp "$DB" "$BACKUP" &&
{ [ ! -e "$DB-wal" ] || cp "$DB-wal" "$BACKUP-wal"; } &&
npm install -g @openrig/cli@0.7.20 &&
rig daemon start --db "$DB"

A failure stops the following commands; fix it before continuing. Back up and install only after rig daemon stop prints the line Daemon stopped: that is the stop outcome that confirms a clean shutdown. Its other success line, “No daemon target recorded; listener refused. Nothing to stop; prior drain not certified.”, means this stop has no recorded target. It does not prove that no daemon exists or that the last one shut down cleanly. A Daemon stopped from rig daemon status does not confirm a clean shutdown either.

If the stop failed or had no recorded target, make sure the daemon is running on its original home and database (start it with rig daemon start --db "$DB" if rig daemon status does not say it is running), then run the whole block again. If the stop is still unconfirmed, use daemon-shutdown.json and daemon.log in your OpenRig home, together with rig context get help, to resolve the reported problem before retrying. Do not continue to the backup or install on an unconfirmed stop.

A clean stop after restarting confirms only the new daemon’s shutdown, not whether earlier unfinished actions completed. Each stop replaces daemon-shutdown.json; look in daemon.log for earlier shutdown failures.

Three additive migrations apply at the first start: 176_node_statusline_throttle (the status-line throttle setting), 177_workflow_bound_pod (a workflow instance's pod) and 178_seat_pool (the seat pool's storage). Migration 178 applies whether or not you declare a pool. Keep the backup: downgrading the migrated database to 0.7.19 is not established. Bundled openrig is 0.7.20; openrig-core is 0.1.34.

A person's own agent

The rigs skill opens with the consent rules an agent must hold from its first handoff, even if it reads nothing else, and points to step 2 for the full rules. It hands work over with a return route: most of the team's questions come back to the person's conversation, and the result is in the handed-over task's resolution, which the agent reads with rig queue show <id> --full. This release ships that guidance; it doesn't claim a measured change in how agents behave. rig setup's next steps and the install reference say the same. (#3500)

The openrig-user skill says that Claude Desktop picks up the team's work with a scheduled task, in a fresh session, and that Monitor is for a session kept open. The rigs skill can be added to OMP (Oh My Pi), installing the shared skill only. (#3503, #3509)

Recovery and delivery

When the tmux server a seat depends on goes away, the daemon records it once and holds automatic delivery to that server's seats. It probes read-only every 5 s, backing off to 60 s, without starting the server, and offers owed work again when the server answers. An explicit rig send is still attempted. rig status, rig ps and rig doctor report the outage. (#3448)

When a parked row's wake is refused at a Claude seat that has reached its usage limit, the wake's record says so and retries at the stated reset; Codex states no reset, so a Codex seat's wake keeps its ordinary retry. A Codex seat's generation record is read from its declared home. rig seat status reads a seat left at a bare shell as needing attention, as rig ps does. rig daemon stop acts on a start reservation's child only after confirming the reservation still names it. Queue-only manual compaction prepares under the lifecycle lease. The draft guard recognizes its own collapsed paste. (#3508, #3507, #3515, #3447, #3465)

These change how recovery and delivery decide. This release doesn't claim a measured recovery improvement on a running team.

Workflows, scope and status

A workflow instance can be bound to a pod. A workflow packet's Continuation line names --evidence-ref when its step needs a receipt, as rig workflow show does, and rig workflow route and rig workflow resume point to that exact command. Scope and proof default to the calling rig's project. Current-state progress updates carry a timestamp. An empty plan lock written with CRLF line endings is refused. Block notes are kept beside continuations. (#3161, #3533, #3151, #3156, #3517, #3499)

One workflow's unreadable mission no longer hides the attention view's other outcomes. A renamed project keeps its rows by its declared former ids, and rows no project claims are counted. Changes to files.allowlist and progress.scan_roots through the daemon's settings API are recorded on the event stream on a best-effort basis after saving; direct rig config set and rig config reset writes are not covered. (#3492, #3267, #3373)

Settings, seats and tools

An opt-in per-seat throttle limits how often the Claude status line is collected. rig provider bindings report what each seat is configured to use. rig start can select fresh seats. A settled Slack question card names the chosen option, redacted as the question card is. (#3433, #3469, #3337, #3519)

A model member can declare a seat-pool block, which is stored on its node, and a sizing planner exists for the pool. Nothing arms or dispatches a pool in this release: declaring one changes no seat's behaviour. (#3480, #3478)

The TUI degrades its control socket instead of ending the launcher, completes commands with leading whitespace, and measures health findings in terminal columns. The CLI aligns node rows by terminal column width, normalizes explicit daemon URLs, and brackets IPv6 targets in rsync operands. Mission and slice reads ask for the proof policy once per request, and slice-term matching runs in one pass; this release doesn't claim a measured speed-up. (#3379, #3489, #3490, #3491, #3523, #3521, #3467, #3468)

Known limits

  • While a tmux server is gone, a stale probe observation can still release or reapply the delivery hold. Later observations correct it, with no guaranteed recovery time. The outage record is in memory, so a daemon restarted during a loss records it again.
  • A restore or rig start can label a Claude seat resumed before its conversation is confirmed, including when Claude reports that no conversation was found. A send can still land on Claude's workspace trust dialog. Check the seat's screen after a restore or start before relying on it.
  • A rig send message sent while Claude's AskUserQuestion dialog is open can become the answer to that question. This was observed on Claude Code 2.1.322 and 2.1.323 with both OpenRig 0.7.19 and 0.7.20.
  • Linked Codex configuration files keep version-specific hook-trust limits, as in 0.7.19. This release doesn't migrate existing noncanonical state or include the linked-path alias change. Review any hook prompt yourself; don't treat this upgrade as prior consent.
  • The seat pool's migration and stored block apply on upgrade even though nothing arms a pool.
  • A return route records where questions should go; it doesn't guarantee arrival. Choice prompts and other hosts keep their own paths.

Credits

Thanks to Ary Rabelo, Dery Ferdika, Devulapalli Naga Sri Vaishnavi, Edward Bowie, Mike Schwarz, Roberto Campos, Samuel Smith, Wu Shuwen, and billbenetti. Their contributions also improve the daemon's memory-limit reasons, tests, CI on Ubuntu, the custom-view SQL contract, Claude readiness polling, startup probing, and documentation.