Repository navigation
OpenRig 0.7.12
OpenRig 0.7.12 is a patch for people running their own agent teams, cut from
main 16e8b7fb. When you answer your team, by typing, clicking or qualifying
an answer, the answer now goes to an agent that reads it with the question and
decides. When no receiving agent is available, your answer waits. Setup's
guidance asks your agent to offer to register you as the team's person, and
registering works when you ask for it. rig down no longer stops a terminal it
can't show belongs to the seat. There are fixes across delivery, Codex,
restore, the queue, Slack and speed, many contributed by people using
OpenRig. Two repairs aren't in this release, and some checks weren't run: see
Known limits.
Before you upgrade
-
rig downis more careful. It stops only a tmux session that carries the
seat's ownOPENRIG_NODE_ID, on the server and session it read. A terminal
OpenRig didn't create, a mismarked one or a replaced one is left running, and
rig downexits 2 naming it and how to stop it yourself. A seat joined with
rig attachas an external CLI is listed as not stopped, since OpenRig never
stops it; that alone doesn't makerig downexit 2. (#2962) -
Adopted tmux sessions:
rig downcan leave them running, even when
rig seat stopsuggests that route. To end only an adopted session, use
rig unclaim <session>to release it from OpenRig, then end that process
and its tmux session. Unclaim leaves the process running; closing only the
viewing window does not end it. -
openrig-core is 0.1.28. A Codex session kept running across the upgrade
can ask for hook approval until it's relaunched.
Answering your team
- Answers nothing else reads, such as a host pairing request or a mode's
scheduled end, use the configured receiving agent or the kernel operator.
Answers wait when no receiver is available, and nothing decides them
meanwhile. To decide one yourself, use its own command:rig host approveor
rig host denyfor a pairing request,rig seat decide-permissionfor a
runner's request. Closing an ask isn't permission, and words that were kept
aren't a default permit. (#2923) - Pairing answers go to the receiving agent, and you can decide directly in the
TUI's pairing settings. A pairing request says who it went to and who reads
the answer. (#2931, #2935) - A runner's permission answer goes to the receiving agent, which decides while
the runner waits, so a qualified answer such as "only if it's the test file"
is read before anything acts. Your answer is kept and an explicit decision
works, but the runner's confirmation updates to you aren't written in this
release. Don't expect a confirmation in the Feed, a notice of the receiver's
state or an immediate wake: the decision reaches the runner at its next read
(up to about 21 seconds in testing). To decide one yourself:
rig seat decide-permission <askId> --option <id> --reason "…". This is the
runner's path only: a pairing request says who reads the answer, as above. (#2934, #2938, #2950, #2966) - Setup's guidance asks your agent to offer to register you as the team's
person. In testing the agent didn't reliably make that offer (0 of 5 runs).
Registering works when you ask for it:rig gateway human add. Nothing is
registered without your yes, an existing default person is kept, and no person
is chosen automatically. The empty-registry hint is right. A team you start
from your own assistant fits your own logins,
with a review before anything is committed. (#2924, #2905)
Harnesses and connections
- A community harness can declare
protocol: pi-rpc, presets can carry launch
wrappers, and a seat can switch between Pi and another runtime. The
community-maintained nodecode runner is listed in the reference.
(#2870, #2759, #2669, #2859) - A relay connector that can't accept incoming connections can pull pending
messages for a person instead of being pushed to: set
OPENRIG_RELAY_MODE=pullin the relay secrets file. Push stays the default.
A person's gateway binding can be unset. (#2844, #2812) rig terminal open <view> --provider herdr-appopens a Rig view inside the
herdr-app desktop window. (#2744, #2956, #2981)
Queue, scope and seats
- Queue content can be erased for closed-work retention and account deletion,
and a retried create can't bring erased work back. (#2837, #2843) - Each send records what's known about its delivery in one
transport.delivery_evidenceevent: what was admitted, what reached the
input, what the screen check showed, and for which occupant. (#2937, #2943) rig queue createadvises on an unresolved scope, slice lists show observed
queue counts, a proof policy can require every listed judge, the execution
ladder shows each slice's recorded status,rig queue shownames a handed-off
row's successor, and a custom blocker ID explains the wait.
(#2901, #2902, #2867, #2872, #2874, #2983)- Every seat's managed guidance points to its skills, help and project context.
rig seat statusshows when guidance was written relative to the session's
recorded moments, and what
the seat's refocus hook recorded. A rebuilt seat's briefing lists older recaps
as optional history. (#2918, #2920, #2916, #2876)
Fixes
- Delivery and drafts: Claude seats with a custom status line read idle and
verify sends; a fresh idle hook doesn't type into a current Claude dialog;
Claude's context hint and drawn cursor are read correctly; when the input
can't be read, a deliberate override (--dangerously-interact) pastes with a
warning and doesn't press Enter, so it isn't submitted; update notices beside the
paste hint are recognized. (#2807, #2813, #2947, #2942, #2933, #2800, #2786) - Codex: when you answer a Codex choice prompt, a message waiting on it is
delivered instead of escalated; a working counter is compared only within one pane process; hook
trust records are written under smol-toml 1.9, so launches no longer stop at
"Hooks need review". (#2952, #2980, #2804) - Restore, start and handover: owed restore input is delivered after a
bounded wait on unknown readiness; compaction uses the draft defaults and
reports repeated unsent preparation;rig daemon startarchives a start
reservation left from an earlier boot; the kernel restart guidance describes
the existing recovery; an earlier occupant can't replace a Claude seat's
resume target; token switches keep the Claude launch; rebuild continuity and
Codex launch choices are explained.
(#2818, #2799, #2797, #2915, #2965, #2796, #2853, #2906) - Queue and recovery: a polling hosted member (an outside assistant on the
team; experimental and off by default) gets one standing notice; a hosted
member's ring that times out reads unknown, and durable recovery doesn't
repeat that recorded wake (other recovery paths can still ring it again);
unroutable items wake as soon as the seat is reachable; the stuck sweep counts
a finding once; an escalation keeps its owner through a handoff; findings route to the
seat's own fallback; a park on an outside condition with no wake says so;
rig workflow validateis read-only.
(#2864, #2957, #2790, #2824, #2946, #2865, #2851, #2852, #2817, #2763) - Slack and people: a Slack reply that can't be read says the message "may
have posted"; threads are recovered when needed; an ask settles after its
original message is deleted; eligible asks post when quiet hours can't be
read, marked when OpenRig can't fully check them; a held ask whose person has
no connector closes as no-connector; update delivery is described without
assuming Slack. (#2909, #2788, #2792, #2814, #2805, #2815, #2927) - CLI and config:
rig context recap-writewrites where every reader looks;
config accepts two keys the daemon already resolves;rig whoamisays the
team is still being built duringrig up; rigs with@in the name find
attention; a seat waiting on a person names its question; the installer
reports PATH gaps with shell hints; daemon credentials stay out of a tmux
server's environment from its next start (a server already running keeps its
old environment until it restarts). (#2914, #2969, #2955, #2949, #2891, #2888, #2883, #2850) - Pi and OMP: typed edits submit in order on the affected Node releases
(22.21.x to 22.22.0, 24.9.0 to 24.11.1, 25.0.0 to 25.1.0) instead of appending an
insertion at the end. (#2847) - Terminals: a Herdr grid whose blank filler cells have no label is confirmed,
instead of reading every seat unconfirmed. (#2849) - Speed: queue listings,
rig queue showandrig parkedstop re-reading
each item;
the stuck sweep yields by elapsed time; Markdown section ends are found in one
pass. (#2825, #2926, #2833)
Behaviour that changed
- Your answer goes to an agent. Through 0.7.11 some answers acted on the
request directly, and some had no receiver when no operator was set. Now these
answers use the configured receiving agent or the kernel operator, with the
question included. Answers wait when no receiver is available.
(#2923, #2931, #2934) rig downleaves terminals it can't show belong to the seat; see Before
you upgrade. (#2962)- Codex "Hooks need review" with smol-toml 1.9 no longer needs a manual
workaround. (#2804) - A daemon start reservation left after a reboot is archived by
rig daemon start; don't clear it by hand. (#2915)
Known limits
- Not in this release: the daemon can pause for up to about a second while
reading proof on large mission trees (#2970), and delivery to a Claude seat
showing Claude's auto-update failure footer can stall because that footer
isn't recognized (#2948). rig down: a terminal it leaves running stays running until you stop it.
It doesn't keep a stored host or boot identity, doesn't guard against another
program running as you, and a daemon restart between losing the tmux server
and the stop wasn't exercised. (#2962)- Codex working counter: a capture that doesn't name its pane keeps the old
comparison, a restart that keeps both the pane and its process id isn't seen,
and a leftover live frame can count once until it expires. (#2980) - Custom blocker IDs explain the wait, but their progress gives no event
wake; the timer remains. (#2983) - Delivery evidence records what was known, not that the agent read the
message; where the input ended up can read unknown. Events are best effort, so
a missing event isn't proof nothing was sent. (#2937, #2943) - Runner permission answers were run end to end with a real receiving
agent and the example runner, whose requesting agent was a stand-in; a
model-driven runner waiting on a person's answer hasn't been run. (#2934) - herdr-app views are one-shot; following isn't claimed. Pull relay
needs a connector that implements pull. (#2744, #2844) - A receiving agent you choose (
agents.operator_session) that runs in an
explicit or auto permission mode gets no OpenRig allowance for
rig host approveorrig host deny, so Claude's review can refuse them. A
kernel receiver in auto mode is included. The default kernel with the default
policy passed at its tested scope. - A receiver that was stopped and then started may not act on an answer that
waited for it. In the tested case where it needed to ask you something back,
the question appeared in its own conversation, not in the Feed or Steering. - Delivery isn't fixed in general: a footer row OpenRig doesn't recognize can
still hold a delivery (#2925), and a held message's full envelope can stay held;
clearing a draft doesn't deliver it (#2515). - Not run for this release (not run, not passed): the two-seat Codex journey
withAGENTS.mdrestore; Codex account-home, upgrade and continuity checks;
the OpenShell worker's second report; Pi model switches on real providers; ACP
in a desktop app; Slack directory paging; some Slack setup cases (channel and
thread precedence, a stopped receiver's delayed pickup, an inherited inbound
default, a plain yes with no receiver); native checks of #2786, #2799, #2807
and #2813, with #2947 partly; a button-and-words answer, a non-pairing ask
with an explicit owner, Steering's Approve page, and these answer and setup
checks on a default model (the tested runs used smaller models);
--wait-for-kernel(#2888), the installed effect of #2800, and #2720 beyond one
platform. - From 0.7.11: its known limits still apply, except Codex hook setup
with smol-toml 1.9.x (#2720), fixed by #2804. 0.7.12 changes openrig-core
again, so the Codex hook note there applies to this upgrade too. They weren't
re-checked for this release unless named here.
Credits
Thanks to @billbenetti, @oodadoudou, @DeryFerd, @Aummadour, @seanmcn, @w4rc0n,
@ziadeh, @vanducng, @smota, @sn1thy, @dajiaohuang and @Vaishnavi220506 for
merged contributions, and to @KM199, co-author of #2947 and #2952, which finish
their #2513 and #2515.
Thanks also for the reports behind these fixes: @nassersala (#2955), @djuntgen
(#2804), @todd-dhango (#2851), @Kayhusk (#2796), @pr0xc3nt4ur1 (#2849 and #2850), @amsayfi
(#2776), @oodadoudou (#2847) and @CaptObvious (#2933 and #2942).
Late verification update: a real Codex lifecycle journey passed its tested launch, same-conversation snapshot restore, existing-rig resume, Core restart with native sessions retained, and fresh-handover task cases. The packaged notes still list that journey as not run because this result arrived after their seal. This does not establish all models or all bidirectional team workflows.
Known limitation: a Codex snapshot restore or rig up --existing can write OpenRig's managed guidance blocks into a tracked AGENTS.md, leaving the worktree modified. Check git status after either operation. Snapshot restore was already disclosed in 0.7.11; the existing-rig trigger is newly observed, and its regression status is not established. A repair is selected for 0.7.13.
The Codex account-home smoke is partial: launch passed, while the account switch was not run after its dry-run requested a named saved profile. Codex ring-2 upgrade coverage and the Codex half of the person-setup checks remain not run at this release decision. The other limitations and coverage omissions in the release notes still apply.