Skip to content

OpenRig 0.7.19

Latest

Choose a tag to compare

@mvschwarz mvschwarz released this 19 Nov 06:24
· 59 commits to main since this release

OpenRig 0.7.19 improves how a team brings permission prompts to a person, reports interrupted recovery, and starts again after a failed launch. It also adds optional Claude hook delivery, per-seat Linux memory limits, and a versioned interface for apps answering human questions.

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.19-$(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.19 &&
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.

Three additive migrations record the hook bridge, each session's launched folder, and app access. Keep the backup: downgrading the migrated database to 0.7.18 is not established. Bundled openrig is 0.7.19; openrig-core is 0.1.33.

Questions and consent

A permission prompt can reach the existing alert route even when its seat has no open work. A recovery waiting directly on that prompted seat or row no longer hides the prompt. Clears from an earlier occupant do not clear the current occupant's alert. (#3425, #3446)

The installer guidance keeps your conversation unless you choose the operator's pane, and teaches reloading a skill added during the session. The guidance says an answer covers that prompt, rather than permission to answer unrelated prompts later. (#3423, #3431, #3454)

Recovery and delivery

Restore now reports skipped saved hooks and missing working folders as gaps. Restore's working-folder projection skips a folder confirmed absent; adapter home/state setup is separate. A fresh launch from a spec can still create its declared folder. Recreated seats' notices and receipts agree about which seat launched, and a delivered sequence can close its notice. Closure is best-effort if bookkeeping fails; a later sequence can still owe work. (#3430, #3436, #3450, #3350, #3415)

launch --fresh can replace the shell left by a failed start without --stop. Fresh launch can reopen a terminal server after a host restart when the old process is confirmed gone. A missing tmux server is reported as a detached session, with guidance to restore or relaunch the seat; unavailable readings remain uncertain. Duplicate automatic watchdog registration no longer aborts startup. (#3392, #3435, #3429, #3443)

For a seat you type in, rig seat set-typing-guard <seat> --mode queue-only --reason <text> keeps ordinary automatic notices out of its input. Watchdog reminders can be noted on a matching row or recorded in a new queue row without a nudge; parked-owner reminders remain retained. Interrupted reminders survive daemon restart. Other delivery modes keep their own behavior. (#3418, #3461)

Claude hook delivery is opt-in: rig seat set-hook-bridge <seat> --enabled true --reason <text>, then inspect rig seat hook-bridge <seat>. On supported Claude versions, launch or restore installs the bridge; it takes messages only after this occupant's waiter has armed. Until then, ordinary typed delivery applies. If an already-routed bridge becomes unavailable, fallback follows the existing delivery checks and names why. The help's 20 seconds is not an arrival deadline: queued work, waiter state and the existing delivery checks determine waiting and fallback. A hook handoff is not proof the agent read or acted on it. (#3270, #3445)

Settings and connected tools

On Linux with systemd, process_limits: { memory_max: "512M" } requests a per-seat memory limit alongside tasks_max; swap is separate. rig seat status shows the observed limit and counters. A limit that cannot be verified is reported, not silently claimed effective. Recovery may attempt a launch without a process limit, with a warning; that attempt can fail. An uncertain or already-started command is not repeated merely to obtain the limit. (#3417)

Apps can use the versioned human-answer interface to read questions, submit answers and recover receipts. Credentials identify an app and permitted actors; they are not private per-person logins. Other improvements bind external input to its run, add optional webhook signatures, and pass advisory participant fields through rig_team. (#3426, #3420, #3364, #3396, #3410)

Capable runners offer rig seat cancel <seat> --run-id <run> --native-turn-id <turn> --request-id <id> for the exact target from rig seat status <seat> --json. Inspect its requested, cancelled, not-this-turn or not-supported result. Neither permission withdrawal nor an accepted cancellation request proves the operation stopped; raw Claude/Codex TUI seats do not gain this runner capability. (#3364)

Known limits

  • A later unreadable tmux sample can show recorded running again after an earlier stopped reading. “Liveness unconfirmed” is not evidence of a live process; inspect the seat before relying on that label.
  • Linked Codex configuration files retain version-specific hook-trust limits. This release does not migrate existing noncanonical state or include the linked-path alias change wholesale. Review any hook prompt yourself; do not treat this upgrade as prior consent.
  • Queue-only reminders are not exactly-once: a lost note receipt can repeat a note. Check the row before acting twice.
  • Downgrading past the Claude hook exec change can leave generated settings unrecognized by the older daemon. Keep your settings backup and inspect them before restarting an older release. (#3427)
  • Manual compaction preparation can be held at queue-only. Inspect rig compact <seat> --state and rig seat held-messages <seat> before deliberately choosing an existing delivery route or level; changing the level does not replay retained messages.
  • A return route records where questions should go; it does not guarantee arrival. Choice prompts, foreign or conflicting routes, existing delivery custody, and a relay that cannot be made keep their existing paths. Tasks at a conversation's address are read on its next turn. When checking open routed tasks, include blocked rows: OPENRIG_SESSION_NAME='<recorded address>' rig queue list --owned --state pending,in-progress,blocked.

Credits

Thanks to Dery Ferdika, Devulapalli Naga Sri Vaishnavi, Edward Bowie, Evgeny Zotov, James B. Shields, Mike Schwarz, NIKHIL, Roberto Campos, Samuel, Samuel Smith, Wu Shuwen, billbenetti, and dependabot[bot]. Their contributions also improve terminal column sizing, JSON errors, transcript searches, workflow ownership, account-label display, scope links, cleanup and documentation.