Repository navigation
OpenRig 0.7.15
[0.7.15]
OpenRig 0.7.15 is a patch for steadier, more truthfully reported teams. A busy
daemon does less repeated synchronous work on a few read paths and names more
of what it was doing when it stalls. rig daemon start waits longer for a slow
start, and restore tries a saved conversation when an eligible seat has no
saved startup context. There are fixes across delivery, Slack replies, Codex seats and
connected assistants, many contributed by people using OpenRig. See Known
limits for what this release doesn't fix.
Before you upgrade
-
Stop the daemon, back up the database, install 0.7.15, then start the
daemon. Your agents keep running through a daemon restart; don't use
rig down, which ends them.rig daemon stop cp "$(rig config get db.path)" "$(rig config get db.path).before-0.7.15" npm install -g @openrig/cli@0.7.15 # or your existing installation method rig daemon start
-
One migration runs before the daemon listens. Migration 165 adds four
columns and two indexes toactivity_grants, binding a runner's activity
credentials to its actual launch. Going back to 0.7.14 after it isn't
established; keep the backup. (#3060) -
A slow start:
rig daemon startnow gives the daemon child it started a
180-second readiness budget, instead of 20 s, and prints
"Waiting for daemon child readiness (…s elapsed; 180s limit)" about
every 20 s. A quick start still returns at once, and a child that exits ends
the wait. Let the wait finish. The budget bounds scheduling: synchronous work
can run past the budget. A child still not ready when that budget is
exhausted is reported pending as before: "Daemon startup is pending after the readiness deadline".
Readiness remains unconfirmed; the child keeps running and the startup
reservation is retained. Inspect the address and log it prints, and don't
start it again until its restart steps are done: stop the named child PID and
wait for it to exit, inspectdaemon-start.lock, and only when both recorded
launcher and child PIDs are absent, archive the lock and run
rig daemon start.rig daemon stopcannot stop that unpublished child. (#3118) -
The plugins: the
openrigplugin carries the CLI's version, 0.7.15.
openrig-core moves to 0.1.30, because its skills changed.
Under load
- The wake ladder reads its prompt-refusal candidates from the open rows,
instead of scanning the whole transition log on every tick. It returns the
same rows. This removes one repeated scan; it isn't a measured fix for every
stall. (#3098) - The execution view's candidate read steps through the queue in windows and,
on its cooperative path, yields to the event loop between them, so a mission
filter that matches few rows no longer holds the loop for a whole history
walk. One large row, or the history count, can still take time. Inside a
transaction, on a memory or temporary database, or on a non-WAL file, the
candidate read keeps its synchronous fallback. (#3122) - Snapshot refreshes share process listings where each seat's order and the
2 s freshness allow; each seat still gets its two ordered observations and
its own fallback. The reduction is derived from the source, not measured. (#3154) - The slow-operation log adds three queue sites and three selected steps of an
ordinary nodes read:nodes.inventory.build,
nodes.inventory.activity_syncandnodes.inventory.terminal_work. These
nodes records are written after a slow call completes; a missing record does
not rule out unfinished work or work outside those steps. This changes no
behaviour. (#3100, #3138)
Restore and seats
- For an eligible seat in a rig with pods that restore starts in its own pane,
a resume token with no saved startup context now lets restore try the saved
conversation with an empty plan. It records thestartup_contextgap. A
successful resume with that gap makes the rig readpartially_restored; a
missing conversation or failed start keeps its own status. No saved startup
plan is replayed or saved startup-context row written; the adapter's ordinary
bootstrap and existing skill restoration still run. An external CLI
attachment is kept, no-token seats still wait for a decision, and legacy
seats are unchanged.restore-checkreads an eligible seat with a token
yellow; for one with no saved context and no eligible token, it points to the
read-onlyrig up <rig> --existing --planpreview. (#3177) - When
rig seat restart --keep-conversationrefuses a recoverable seat whose
tmux session is gone, it names the way back:rig launch '<rig>' '<node>'
(add--planto preview). (#3135) restore-checkand a full restore warn when a snapshot recorded a named
Codex profile that the current seat has cleared; restore uses the current
selection. Nothing is refused. (#3155)- A context-usage watchdog reads its own seat's current occupant, not an
archived generation's. A context watch whose seat can't be pinned, or has no
recorded tenure, skips that tick with its reason instead of ending. (#3027, #3139)
Delivery and people
- Right before an automatic paste into a seat with the draft-aware guard,
OpenRig re-checks: it holds the paste after recent client activity, re-reads
the input after a short wait, and holds when tmux can't be read. The message
is held and retained;rig seat held-messagesshows it. An ordinary guarded
paste waits about 300 ms longer. This narrows #3076's window; it doesn't close it.
This is shown by the change's own tests; it's not yet checked with the real
programs on this release. (#3097) - A terminal seat whose tmux session runs under another name gets the exact
text of a send, and a queued wake no longer types OpenRig's From/To envelope
into its shell. (#3074) - When the arrival note is recorded before the answer is routed, an answer to
a reply in an older Slack thread posts back into that thread, not as a new
top-level message; see Known limits for when it posts top-level. Only the
conversation's newest thread answers a parked question, as before. (#3120) - Slack previews on posts to a person are a setting:
rig slack setup --unfurl on|off,
andrig slack statusshows which is in effect from the connector's next
rewire. The default is off; see "Behaviour that changed". (#3157)
Connected assistants
- An assistant that passes its team's display name as
rig_team'srigIdis
told to leaverigIdout to see its own team, and a hosted member with no
wake trigger is told it picks up work when its person asks, or on a schedule
they set. (#3104) - An external grant that works its own inbox is told only about the tools it's
offered. (#3140) - The TUI keeps connected assistants' check-in lines when a rig's seat
inventory can't be read, with the error beside them. (#3105) - The
openrigplugin needs Claude Code 2.1.119 or later. On earlier versions,
with the plugin's OpenRig seat setting left blank, Claude Code drops its MCP
server: the skill loads, but the agent has no OpenRig tools. (#3137)
Codex, runners and harnesses
- OpenRig renews its own changed Codex hook approvals. When a new
openrig-core changes one of OpenRig's six Codex hook declarations, the launch
that installs it renews those approvals from OpenRig's own record instead of
stopping at Codex's hook review. This runs at daemon start in the daemon's
Codex home, when hooks are on and a Codex seat selected openrig-core, and at
each such seat's launch in its own Codex home. It renews only when the
installed plugin matches the shipped one and every current approval matches
OpenRig's saved record. A person's own choice in any layer OpenRig reads
keeps the review; profile files passed with-paren't read. No real Codex
seat ran in its tests. (#3143) - A Codex seat's resume command in the node inventory and detail panel is
built from what a real resume uses, with a label when the recorded launch
differs. Workspace options that aren't recorded per launch can still read as
a match. (#3043) - Runner activity grants are bound to the actual launch, and the
replacement's activation revokes its predecessor's grant. A grant made before
this release stays tied to the seat's occupant until then. A grant that can't
be bound never blocks a launch or restore. This attributes reports to
the run OpenRig selected; it doesn't prove a runner's identity. (#3060) - Terminal views find tmux again when its cached path is gone, instead of
tiles exiting 126 until a daemon restart. (#3129) - A
SKILL.mdwith CRLF line endings is discovered and reaches a seat's
managed plugin loadout. (#3153) rig context work-install --mission <missing>warns that the mission
doesn't exist, andmissionRootreads null; the exit code is unchanged. (#3141)- OpenRig's own transitions (
daemon@kernelandsystem:*) no longer count
toward ceremony amplification, and the post-restore audit message matches
the restore skill. (#3124, #3127)
Behaviour that changed
- Slack previews: posts to a person no longer show link and media previews
by default. An existing install stops showing them after its next connector
rewire or daemon restart. Runrig slack setup --unfurl onto turn them back
on; earlier previews aren't removed. (#3157) - Restore of an eligible seat with a resume token and no startup context
now tries its saved conversation, and a successful resume reads
partially_restored. It used to stop with "Harness not started: no startup
context" and read the rig not restorable. (#3177)
Known limits
- Daemon start: the longer readiness budget doesn't identify or cure the
cause of a slow start, synchronous work can run past the budget, and a child
still not ready when that budget is exhausted stays pending. (#3118) - Daemon memory: 0.7.14's comparison under load established neither equal
memory nor a regression against 0.7.13. This release makes no memory claim. - Restore's overall result: a rig can still read
fully_restoredwhile a
seat restore didn't start (one claimed or added after its roster or snapshot
was recorded), or a seat kept in its external CLI attachment, goes unnamed.
A seat restore left as a bare shell after "Harness not started" still counts
as running inrig ps.restore-checkcan also say "Restore tries …" for a
self-attached member that restore leaves out; that member isn't restored. - Draft-aware delivery (#3076): typing after the guard's final check and before
the paste can still leave the notice beside the person's draft. In the tested
append-mode schedule Enter was refused and nothing was submitted or deleted;
this is not a guarantee for every interleaving. The prior conditional-send
Enter-window case is unchanged: characters typed during OpenRig's last checks
before Enter submitted with OpenRig's text. - Draft-aware delivery with a wide Claude Code footer: with Claude Code's
full-width auto-update-failure footer on screen (seen at 200x50), a seat in
the opt-in draft-aware typing mode whose input is empty can hold an ordinary
send instead of delivering it. The message is kept, not lost, and
rig seat held-messagesshows it. On 0.7.14, the clipped footer at 80x24
didn't do this. - Draft-aware delivery to a busy Codex seat: on Codex (seen with 0.167.1
and 0.167.2), a send to a seat in the opt-in draft-aware typing mode while
it's busy can be pasted into its input without Enter. The message isn't
delivered, and it isn't kept forrig seat held-messages. A deliberate send
reports failed, and its text stays in the seat's input box. This was seen on
0.7.12 and 0.7.14, and there's no fix for it in this release. - Seats at the edit floor can stop for approval, OpenRig's own commands
included. A Claude seat running at the harness's edit floor can ask for
approval before shell commands, including OpenRig's own read-onlyrig
commands such asrig whoamiandrig queue show. Choosing a built-in
policy such as standard when your team is set up doesn't change that at
launch: the plan showslaunch_posture=floor. Each prompt waits until
someone approves it, in the seat or through your own agent, so a team can
stall while nobody answers. - Approvals your agent recorded: In one Claude setup, your agent recorded
approvals it made itself as "Person approved". Those entries alone do not
establish your approval; check the conversation to see who actually decided. - A new Claude agent's startup text can stay unsent in its input box while
the seat reads ready. Press Enter in its terminal. - Linked Codex config files: when a Codex seat's
config.tomlor
hooks.jsonis 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
linkedconfig.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
intohooks.json. (#3078) - Slack reply threads: recording the arrival note is best effort: a failed
write is not retried and that answer posts top-level. Creating the message
and recording the arrival note are separate writes, so a notification can
also be posted before the note is recorded, with the same top-level outcome.
The person's message is kept. (#3120) - From 0.7.14: its known limits
still apply, except where this release changes them. #3105 fixes the
TUI tables' dropped check-in line, and #3097 narrows the draft-aware paste
window described above, as its own tests show. 0.7.14's other limits weren't
re-checked for this release unless named here.
Credits
Thanks to @dajiaohuang, @Kayhusk, @billbenetti, @Aummadour, @smota,
@vanducng, @zichen0116 and @Nikhila-Dhevi-R for merged contributions. Thanks
also for the reports behind these fixes: @Aummadour (#2989), @vanducng
(#3128), @Alejandro-SJ (#2990), @billbenetti (#2976) and @Kayhusk
(#3131).