Skip to content

OpenRig 0.7.17

Choose a tag to compare

@mvschwarz mvschwarz released this 16 Nov 21:47
· 172 commits to main since this release

[0.7.17]

OpenRig 0.7.17 teaches a team to bring its questions to the Claude Code
conversation you started it from: the installer, the kernel operator and the
rigs skill are instructed to bring a seat's prompt back there, pass on only
what you answered, and read the newest review before saying the work is done.
In this release's first trial, that guidance didn't complete the journey (see
Known limits). Restore and rig down report more of what they actually did,
and there are fixes across delivery, workflows and connected assistants,
including contributions from people using OpenRig.

Before you upgrade

  • Stop the daemon, back up the database, install 0.7.17, then start the
    daemon.
    Your agents keep running through a daemon restart; don't use
    rig down, which ends them. Each step runs only if the one before it
    succeeded. The backup goes to a new, dated file, with its -wal file beside
    it when there is one, so running the block again never overwrites an earlier
    backup. If you installed OpenRig another way, use that in place of the
    npm install line.

    Before running the block or any recovery command, use the same OpenRig home (OPENRIG_HOME, or legacy RIGGED_HOME) as the daemon you are upgrading.

    If that daemon was started with --db, or with OPENRIG_DB (legacy RIGGED_DB) set differently from this shell, replace the block's DB= line with its actual database path instead of using rig config get db.path, and pass that path with --db to every rig daemon start below, including recovery. The config command reads this shell's configuration, not the running daemon's launch settings.

    rig daemon stop &&
    DB="$(rig config get db.path)" &&
    BACKUP="$DB.before-0.7.17-$(date -u +%Y%m%dT%H%M%SZ)" &&
    { [ ! -e "$BACKUP" ] || { echo "$BACKUP already exists and is kept; run the block again." >&2; false; }; } &&
    cp "$DB" "$BACKUP" &&
    { [ ! -e "$DB-wal" ] || cp "$DB-wal" "$BACKUP-wal"; } &&
    echo "Database backed up to $BACKUP" &&
    npm install -g @openrig/cli@0.7.17 &&
    rig daemon start

    If a step fails, nothing after it runs: fix what it reports, then run the
    whole block again. If rig daemon stop fails and rig daemon status then
    says "Daemon stopped", run the block from the DB= line. If it says
    "Daemon PID is absent", run rig daemon start, then the whole block again.
    Keep the backup, and its -wal file, until 0.7.17 is running well.

  • Two migrations run before the daemon listens (168 and 170). Going back to
    0.7.16 after them isn't established; keep the backup. (#3260)

  • The plugins: openrig carries 0.7.17; openrig-core stays 0.1.31.

Your team's questions, in your own conversation

  • When you stay in your own Claude Code conversation, the installer is
    instructed to hand your goal to the team as a task from it. The kernel operator is instructed to
    bring a seat's prompt there with its choices word for word, and to offer a
    seat's terminal only if you choose to watch or answer in the pane. If you
    chose the panes, nothing changes. (#3288, #3306)
  • Also: the launch plan says a team seat with no permission policy gets the
    team default, and every seat's startup text is smaller, with the installing
    procedure loaded from the rigs skill when needed. (#3289, #3238)

Recovering the same work

  • Restore says when it didn't restore everything: a seat skipped because
    it isn't in the snapshot's roster, or left attached, makes the rig read
    partially_restored. An adopted seat keeps a usable recorded session name;
    otherwise restore names the old and new address. (#3260)
  • Two opt-in daemon routes: resume one banked original conversation, and
    hold one rig's automatic delivery during maintenance until an explicit end.
    See docs/reference/daemon-http-clients.md. (#3260)
  • A restore that can't confirm it stopped a blank session keeps that
    session's record and binding, reads attention_required, and says the session
    may still be running: check it with rig capture and stop it with
    rig seat stop. (#3258)
  • rig down releases a claimed tmux session (self-attached inside tmux,
    adopted, bound or reconciled) instead of failing: it prints
    Released, not stopped: <session>, leaves the session running and exits 0. An
    external CLI attachment is unchanged on down, and rig remove of one no
    longer fails with 409 kill_failed. (#3263, #3272)
  • Claude resume: a pane that moves during resume-token capture leaves the
    token unknown. (#3262)

Delivery, workflows and tools

  • Three daemon read paths changed: the stuck sweep yields between windows of
    undelivered work, Codex thread lookup reuses new log rows on warm reads, with
    full cold and fallback reads, and a work node's SPEC.md is reread only when
    its file changed, within a two-second settle window, or when that can't be
    read. This release makes no speed claim. (#3285, #3295, #3296)
  • Draft-aware delivery reads an empty input box under Claude Code 2.1.322 or
    2.1.323's wide paste hint and auto-update failure as empty (checked with
    Claude Code 2.1.322 and 2.1.323 in a test run). (#3231)
  • Claude's question dialog, in the several-question, editor-shortcut and
    preview layouts OpenRig recognizes, refuses an ordinary send (shown by its
    tests; not yet checked with Claude Code itself). (#3256)
  • Clearer refusals at a model picker (close it with Esc) and under managed
    disableSideloadFlags. (#3207, #3247)
  • A resumed Codex conversation isn't told to sign in again because of an old
    token-refresh failure that newer output follows. (#3248)
  • rig provider switch --token-file keeps the Claude token step for pane
    readings it used to drop, and after a failed correction only for a session
    proven to be this seat's. (#3278)
  • Work for a hosted member with no wake trigger reads awaiting-pickup:
    instead of unroutable:: it waits in its queue until the member reads it. (#3222)
  • Workflows: rig workflow revise can drop an obsolete required order from
    unstarted work, and a replayed route adoption without --packet writes
    nothing. (#3276, #3266)
  • Assistants and tools: an external connection's rig_queue_show labels who
    acted apart from the reader; the TUI can read a remote rig's seats with
    ui.topology_remote_seats (off by default); a Pi or OMP runner pane names its
    model and state; rig bundle check reports schema-invalid configuration
    names; and the text output of rig network status hides a hub URL's query
    (--json is unchanged). (#3234, #2922, #3212, #3160, #3207)
  • Also: account-rig erasure, OpenShell recreation after a socket change, and
    handoff reconciliation hints. (#3190, #3291, #3217)

Behaviour that changed

  • An empty person registry reads undeliverable:no-registered-human. (#3288)
  • rig send --dangerously-interact without --type-without-checking stops
    on a person's text under Claude Code's wide footer row (shown by its tests;
    not yet checked with Claude Code itself). (#3231)

Known limits

  • Questions in your own conversation wait for you: nothing wakes an idle
    conversation, and a prompt that changes between OpenRig reading it and sending
    your key can take the key. In this release's first trial, with Claude Code
    and a simulated person, a reviewer's permission question never reached the
    person, the person's agent twice offered a bare terminal attachment as a way
    to answer a seat's prompt, and the work didn't reach a reviewed commit. No
    return address for the person's conversation had been established, and no
    escalation for the reviewer's question was recorded. This guidance doesn't
    reliably complete that journey, and a second trial wasn't run.
  • Restore: restore-check's recovery plan still counts seats restore leaves
    alone, and a seat left as a bare shell after "Harness not started" still
    counts as running in rig ps.
  • rig down: a second down while a released session runs reports its kept
    skills as an error and exits 2. After rig down --delete, a later down of
    another rig in the same folder may remove OpenRig's shared guidance there.
  • A Codex seat resumed on Codex 0.167.1 or 0.167.2 can read unknown when
    its resume header or update notice names that version.
  • rig scope and rig proof can't be limited to a rig's own project. (#3026)
  • Reading queue state with rig queue list: the median time was about 22%
    (about 90 ms) slower than 0.7.16 in a matched test on a pre-release build. The
    cause wasn't found, and the final build wasn't re-measured.
  • Linked Codex config files: when a Codex seat's config.toml or
    hooks.json is a symbolic link, OpenRig records its hook trust under the
    link's target, as in 0.7.14. A change to key it by the file's own name isn't
    in this release, and such a seat may be asked to review hooks again. With a
    linked config.toml, OpenRig can also miss a setting stored for it that
    turns OpenRig's hooks off, and set those hooks up anyway when it moves them
    into hooks.json. (#3078)
  • Approvals your agent recorded: in one Claude setup, an agent recorded
    approvals it made itself as "Person approved"; check the conversation to see
    who decided.
  • Slack buttons: in 0.7.16's tests, an answer given by button wasn't seen to
    reach OpenRig, and the cause isn't known. Type the reply instead.
  • From 0.7.16: its known limits
    still apply unless this release changes them (#3231, #3260).

Credits

Thanks to @dajiaohuang, @EZotoff and @Kayhusk for merged contributions. Thanks
also for the reports behind these fixes: @DavKato (#3245) and @Kayhusk
(#3228).