Skip to content

OpenRig 0.7.18

Latest

Choose a tag to compare

@mvschwarz mvschwarz released this 17 Nov 18:14
· 93 commits to main since this release

[0.7.18]

OpenRig 0.7.18 can send a team's seat prompts to the conversation you handed
the work over from, restore says more truthfully what it left running, and
three settings can be chosen per seat: native input, Claude's auto mode and, on
Linux, a task limit. Many fixes come from people using OpenRig.

Before you upgrade

  • Stop the daemon, back up the database, install 0.7.18, 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.18-$(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.18 &&
    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.18 is running well.

  • Four migrations run before the daemon listens (two numbered 171, then 172
    and 173), each adding columns or indexes. Going back to 0.7.17 after them
    isn't established; keep the backup. (#3286, #3339, #3318, #3332)

  • The plugins: openrig carries 0.7.18, and openrig-core moves to 0.1.32
    because its skills and refocus hook changed.

Your team's questions, in your own conversation

  • Hand a goal over with a return route: rig queue create --return-route auto gives your conversation an address, and every handoff carries it
    (--return-route self from a session that joined the team). When routed work
    is held at a seat's prompt, or waits on it, a prompt that isn't a choice
    dialog is sent to that address as a task. Choice prompts, a prompt already
    with the gateway, and a route that can't be used (another host's, two that
    disagree, or a relay that couldn't be made) keep their existing path. The
    rigs skill teaches this; without --return-route, nothing changes. (#3318)
  • Guidance: the kernel operator is instructed to answer a registered person
    where they wrote, without the terminal user's leave (guidance, not proof an
    answer is delivered), and messaging-the-human says how to close the ask an
    answer settles. (#3370, #3305)
  • Slack: a button answer keeps each option's history and who gave it; a
    click that fails to record enters the existing retry path, which fills only a
    still-unanswered question. Settled cards drop the raw closure code ("Denied"
    for a refusal), and the opt-in rig slack manifest --private-channel sets up
    a private channel. An answer through MCP's rig_question_answer is accepted
    when the daemon requires an operator token. (#3353, #3359, #3324, #3344, #3257)

Recovering the same work

  • A seat that restore leaves as a bare shell no longer counts as running in
    rig ps, including a recreated seat, and a seat with a delegation parent or
    escalation destination gets that owner one queue item per restore listing
    each cause and the next step. Launching over a live session no longer says
    "Already running". (#3185, #3216, #3366, #3215)
  • Restoring after OpenRig's home moved: rig up --existing --cwd honors
    --cwd, names a missing saved folder and leaves a folder with a declared
    project unscaffolded, and Claude seats keep OpenRig's core plugin. (#3347, #3352)
  • Restore and restore-check name agents that share a recorded
    conversation
    and leave the choice to you; --plan shows each seat's
    restore permission and its source. (#3250, #3186)
  • rig seat handover --recover reads an interrupted Claude handover more
    truthfully and accepts a successor alone in its session's current window. (#3246, #3369)
  • Also: a later rig down no longer exits 2 over a released session's kept
    skills (a plain down of a stopped rig still exits 1); Codex 0.167.1 and
    0.167.2 seats read their real activity; an adopted, still-running seat's
    hooks read as its own; and refocus orients from the seat's selected project
    when no task is in progress. (#3303, #3182, #3365, #3351)

Queue, delivery and settings

  • Per-seat choices, all opt-in: native input instead of terminal typing
    (rig seat set-input-route <seat> --route native --reason <text>); Claude's
    autoMode block (claude_auto_mode, or rig seat set-permissions --auto-mode); and, on Linux with systemd, a requested task limit
    (process_limits: { tasks_max: N }). A fresh start whose limit isn't seen to
    take effect is refused; a recovery that can't apply it may try without the
    limit, with a warning; and an uncertain start is reported and not retried.
    An export names a stored limit it can't read instead of refusing the rig. (#3339, #3286, #3332, #3390)
  • rig compact on a Pi seat requests Pi's own compaction, and --state
    reports the attempt. (#3013)
  • Queue and workflows: rig queue tag adds tags to an existing row;
    rig queue list names a handed-off row's successors; a handoff advises on a
    mission or slice tag that resolves to nothing; a hold blocked on a custom-ID
    row records its wake; a wake that failed before any input gets one retry on
    the same seat; and rig workflow route adopts a second handoff to the same
    target. (#3281, #3302, #3178, #3152, #3243, #3311, #3363)
  • Terminals and assistants: CLI terminal reads send the configured terminal
    bearer; a custom TMUX_TMPDIR is named in the attach command; with tmux 3.2
    or later, a herdr-app cell at herdr's default hidden size (200x120) no longer
    resizes the seat; tmux credential cleanup can't fall back to a server-wide
    value; rig acp run's log keeps multibyte characters split across reads; and
    network assistants learn the retry rule and pickup timing. (#3360, #3165, #3358, #3342, #3343, #3329)
  • Also: runner reports stay bound to their run, recent transitions honour a
    limit up to 1,000, and the stuck sweep makes fewer reads. This release makes
    no speed claim. (#3150, #3211, #3301, #3340)

Behaviour that changed

  • Each restored seat's checkpoint is its own file,
    .rigged-checkpoint-<session>-<digest>.md; anything that reads
    .rigged-checkpoint.md won't find it. (#3347)

Known limits

  • Prompts in your own conversation wait for you: a routed prompt arrives on
    that conversation's next turn, nothing wakes an idle one, and arrival isn't
    guaranteed. A prompt can still change between OpenRig reading it and sending
    your key. In two measured Claude first-user runs, one agent set no return route. The other completed reviewed, committed work with the route set, but read prompt relays only after the prompts had been answered and approved later prompts beyond the person's one-time consent. Neither run met all first-user criteria.
  • Adding rigs during a running Claude Code session: If installation creates a top-level skills directory that was absent when the session started, Claude Code's documentation says to use /reload-skills (available from Claude Code 2.1.152) to discover it. Starting a new session is an alternative. Neither recovery was exercised in this release's first-user test.
  • Restore: a seat isn't told where its checkpoint file is, and a written
    checkpoint isn't proof it was read. After a --cwd restore, rig down
    doesn't clean OpenRig's Claude settings, hooks and collector from that
    folder. When a full restore recreates a seat, its result can still list it
    as not started, and the attempt's record can miss its actual outcome.
  • Native input route: withdrawing a permission doesn't cancel a native
    seat's work in progress.
  • Queue help says a human seat such as human@host asks no one; that holds
    only for an unregistered one.
  • 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)
  • OpenRig 0.7.17 rejects teams whose exported rig.yaml contains claude_auto_mode or process_limits. Upgrade the receiving install to 0.7.18, or remove those fields from a copy only if you intend to share without those per-seat settings.
  • From 0.7.17: its known limits
    still apply, except the bare-shell count, the second rig down's exit 2 and
    Codex 0.167.1 and 0.167.2's unknown (#3185, #3303, #3182).

Credits

Thanks to @Aummadour, @billbenetti, @cavalcanticampos, @dajiaohuang,
@DeryFerd, @EZotoff, @oodadoudou, @pr0xc3nt4ur1, @shravansumanthanan, @smota,
@Temikus and @w4rc0n for merged contributions. Thanks also for the reports
behind these fixes: @billbenetti (#2725, #3218, #3316), @Kayhusk (#3320),
@parkingmeter (#1933), @z4cc (#313) and @ziadeh (#2487).