Repository navigation
OpenRig 0.7.13
[0.7.13]
OpenRig 0.7.13 is a patch for people running their own agent teams. When you answer a runner's permission request, you now get a
note back saying who decides it, and the runner wakes on the decision. The
agent that reads your answers is told what an answer typed at your machine
means and how to ask you back. rig daemon start tells the agent setting
OpenRig up to offer to register you when nobody is registered yet, and a Claude
seat whose usage-limit message states a reset time waits for it instead of being
retried. There are fixes across delivery,
handover and recovery, the TUI and speed, many contributed by people using
OpenRig. In our tests, a first Claude user (with Codex absent) and a first Codex
user each went from a fresh install to a built, independently reviewed and
committed change. Two repairs aren't in this release: see Known limits.
Before you upgrade
- Back up the database, install 0.7.13, then restart the daemon:
rig daemon stop,
copy the database file (rig config get db.pathprints its path), install
OpenRig 0.7.13 using your existing installation method, thenrig daemon start. Your agents keep running through a daemon restart; don't
userig down, which ends them. Three migrations run on the daemon's first start: 160 and 161 (for the experimental hub connector below)
and 162 (indexes for session reads). Going back to 0.7.12 after them isn't
established. (#2993, #2997) - openrig-core is 0.1.29, and the
openrigplugin now carries the CLI's
version, 0.7.13. A Codex seat can ask for hook approval after the upgrade; see Codex hook review after an upgrade below. (#3034, #3064)
Answering your team
- A runner's permission answer gets a note back to you: who decides it and in
what state, or that it's kept and the tool hasn't run. A runner waiting on
the decision gets it within about half a second. Read that note before answering again. If
it says your answer couldn't be passed on, follow its retry instruction or use
therig seat decide-permissioncommand it names.
(#3001) - The answer a receiving agent reads now says what an answer typed at this
machine's terminal or TUI means, to act on a clear answer with the request's
own decision command, and how to ask you back with a new ask when it isn't
clear. When the default receiving agent asks you back, the question reaches
your Feed, and your reply decides. Closing a runner's request without
deciding permits nothing. (#3030) rig daemon startends by telling the agent setting OpenRig up to offer to
register you as the team's person, when the person registry can be read and
holds nobody. The rigs skill's start step makes the same offer, and asking to
be reachable registers you as the default person directly. In our
fresh-install tests the setup agent passed the offer on in 5 of 6 installs,
and a no registered nothing. Nobody is registered without your yes, and the
exit code is unchanged.
(#3028)- In the change's own tests, before a first team launches, the kernel operator
says which commands it will ask permission for and reuses a choice you've
already made. Otherwise it makes one offer: allow just the command families
your goal repeats, for this project only, applied on your yes. On a no, the
team's default stays and the offer isn't repeated. It hasn't been shown to
make a first team ask you fewer times. (#3029) - A connected assistant (a hosted member; experimental and off by default) shows
whether it's checking in, against a cadence its roster entry states
(check_in_minutes, orcheck_in_on_request: true): checking in, overdue, no
check-in yet, on request, or unknown.rig roster showandfindprint it as
a Check-in line. It's a status only: work for a member that isn't checking in
still queues and rings as before. (#3023)
Seats, handover and recovery
- A Claude seat stopped by a usage limit whose message states a reset time (for
example "resets Nov 10, 4pm") parks its pending work until then, instead of
being retried every few minutes. (#2917) - A handover whose successor was launched but not ready says it may be running,
instead of "retry": look at the pane first. A handover also cleans up the
retiring occupant's own claims and jobs. (#3003, #3024) - After
rig unclaim, the guidance for an adopted session says to end its
process and its tmux session, andrig seat stop's help matches. A fresh
launch afterrig unclaimended the server's last session reopens the server.
(#2996, #3006, #3014, #3009) - A handover whose successor was launched into the seat's own tmux session
can reclaim a claim left by a removed owner, or by an archived owner whose
latest session for that node is superseded, detached or exited; a live owner
still refuses.
When a seat
with no declared route can't be woken, the finding goes to the item's creator,
skipping a creator that is a terminal seat. (#2869, #2987, #2995)
Fixes
- Delivery: Claude's auto-update failure footers, including one clipped form,
no longer hold a send to an idle Claude seat; an unrecognised wake result reads unknown, not
delivered; an ordinary one-time park wake is kept and retried
while its park is current and the failed attempt typed nothing into the seat
(an attempt whose effect is unknown needs checking, and repeating waits and
usage-limit expiry keep their own lifecycle); acustody-verified:note whose target is followed by a
period, comma or other closing punctuation now verifies it; the Pi runner pane keeps the operator's
draft out of the stream. (#2948, #3016, #3011, #3038, #3004, #2842) - Codex and Claude: completed Codex 0.167 turns read idle, and unsupported
versions stay unknown; a usage-limit banner with a curly apostrophe is
detected; refocus bounds Codex context and records what it left out; an
unreadable Claude status-line cache gets its own reason. (#2954, #2879, #2951, #2880) - TUI and CLI: instance rows are grouped by rig; for a quiet seat the
daemon explicitly reads as unknown, the list, explorer and agent-detail status
rows show unknown, not idle (screen motion still shows active, a daemon that
serves no activity keeps the screen fallback, and the topology graph is
unchanged); Feed times use the configured time zone; the
CLI doesn't call a daemon stopped when the shell can't see its process (a
sandbox), and says not to start another; ssh options are separated from the
target, and the generated attach command quotes the session name. (#2857, #3012, #3022, #2913, #2973, #2971) - Scope and workflows: qualified slice reads and proof discovery are scoped
by mission; workflow spec reads are recorded across restarts; the spec library skips
synthetic alias entries. (#2960, #2986, #2999) - Guidance and plugins: guidance cleanup in a repository's
AGENTS.mdor
CLAUDE.mdremoves redundant recognized copies of an OpenRig-managed block,
including after an editor rewrapped a marker, and keeps distinct edited
copies. A saved write record lets OpenRig identify and keep your edits; on a
fresh start, a differing block with no write record is refreshed to OpenRig's
text and named, while an exact resume or restore keeps it; a bundled plugin's files,
including a binary icon, are copied byte for byte; the plugins carry https
repository URLs and a PNG icon for Claude's plugin directory, and the Codex
manifests link the privacy policy and terms. (#3020, #3025, #3021, #3064) - Speed: the daemon is much more responsive while it reads a project's
proof, which now yields between missions; current-session reads for the node inventory
use an index; the daemon's recorder and Linux clipboard discovery no longer
wait on the main thread.
(#2970, #2997, #3019) - Docs: what
rig seat clear-attention's check proves, how managed
compaction notices are routed, when the keyboard moves in herdr-app, a
complete periodic-reminder registration, and starting one stopped kernel seat
withrig launch. (#2964, #2984, #2991, #3002, #3031)
Experimental
rig networkconnects one local seat to a hub you already have.
Experimental, unsupported and at your own risk. The connector uses the MCP
SDK, which the installed package already included in 0.7.12. (#2993)
Behaviour that changed
- A runner's answer is confirmed to you. Through 0.7.12 no note came back,
and the runner waited for its next read. (#3001) - A usage-limited Claude seat waits for its stated reset; don't release it
by hand on a timer. A failed handover may have left its successor
running; look at the pane before retrying. (#2917, #3003) - Passive SSH host status reads
unknown. Routine host listings no longer
open a TCP connection to SSH hosts, because repeated probes closed without a
handshake can make OpenSSH block real logins for a while. Hosts that used to
read reachable now read unknown;rig host doctorstill checks actively.
(#2979) rig package installleaves a guidance file alone when a recognized
managed block has no complete marker pair, lists it under "Left as it is:" and installs the rest, instead
of appending a second copy. Launch and restore name such a file
(guidance_block_markers_damaged). (#3020)
Known limits
- Not in this release: a Codex snapshot restore or
rig up --existingcan
write OpenRig's managed guidance into a trackedAGENTS.md, leaving the
worktree modified; checkgit statusafter either operation. - Not in this release: a person who talks to the kernel operator first, with
no other agent setting OpenRig up, isn't offered registration.rig up,
rig startandrig contextstart the daemon without printing the offer
either. Register withrig gateway human add. While nobody is registered, a
laterrig daemon startoffers again, even after a no; nothing is registered
without your yes. (#3028, #3041 isn't in this release) - The hub connector isn't inert: the daemon starts it, sweeps leftover
credential folders and schedules local rounds even with no binding; only the
pass to a hub is absent. Its migrations apply on upgrade. (#2993) - The recorder: a queued begin record can be lost before the durable append,
and a stalled worker has no acknowledgement timeout. (#3019) - Speed and memory: On one performance host, whole
rig queue create
invocations had a median about 10.4% slower than 0.7.12 (about +29 ms). Send
latency stayed within the comparison's unchanged range. The cause remains
unidentified. The standard idle-memory comparison was inconclusive. A post-hoc
analysis of the same six runs found 7.9–8.6 MiB (4.2–5.3%) higher daemon RSS
across three matched idle windows, using the median of three arm medians per
version. The cause and steady-state behavior remain unestablished. - Draft-aware delivery (#3076): an automatic OpenRig notice can be left beside a
draft started during delivery. This also concerns notices admitted by
openrig-urgent and urgent-only modes. In the reproduced 0.7.12 Claude Code and
Codex cases, the person's draft remained intact and no Enter was sent, but
OpenRig's text stayed in the input. The guard and paste path are unchanged in
this cut; a native 0.7.13 reproduction has not run. - Native model pickers: with a /model picker open, an ordinary send can act
on the picker instead of delivering the message. In 0.7.12 tests it confirmed
Claude Code's already-selected default and advanced Codex's model selection;
neither message reached the model. Close or deliberately resolve the picker
before ordinary delivery. The native 0.7.13 case has not run. - Codex hook review after an upgrade: in one test whose Codex home already
held earlier hook approvals,rig up --existingstopped for hook review in
each Codex pane; approving the hooks resumed all three conversations. A
separate test of the same upgrade on a fresh Codex home, on another host,
restored without review. The cause of the difference is not established. - A first team with Codex installed but signed out: a Claude user's starter
team includes a Codex reviewer that waits for a Codex sign-in, and you aren't
told beforehand. If Codex is installed, tell the person about the possible sign-in wait before the team starts; signing in first was not tested as a remedy. - A first team's permission asks: a command joined with
&&,;or a pipe
still asks unless every part is allowed, and OpenRig's own lifecycle commands
still ask on Claude seats. (#3029) - Usage-limit parking was tested with the limit message from
claude -p. If
an interactive seat's limit report doesn't carry the message, the seat is
retried as before. A reset in the past or more than 8 days away is ignored.
(#2917) - Handover: two other failures can still say "retry" while a successor may
be running: a context delivery failure, and a Codex launch failure after an
update prompt wasn't dismissed. Look at the pane first. (#3003) - Answers: when a receiving agent asks you back, it can stop at Claude
Code's own permission prompt, which you don't see. A receiving agent you
choose can still decline to act on a clear answer. A pairing requester's
description of itself is quoted for the receiving agent, but still shown
unquoted in the request's summary and the notices about it. The TUI's
one-line notice after you answer can clear within a frame. (#3030, #3001) - Proof reads still pause briefly, and a whole read takes slightly longer.
Yielding isn't a hard bound on latency or a single atomic snapshot of the
proof. (#2970) rig downkeeps no 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: delivery evidence records what was known, not that the agent read
the message, and events are best effort. 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). - 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) - 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. - An already-running tmux server keeps its old environment, daemon
credentials included, until it restarts. (#2850) - herdr-app views are one-shot; following isn't claimed. Pull relay needs
a connector that implements pull. (#2744, #2844) - From 0.7.12: its known limits
still apply, except that #2970 and #2948 are now in this release,
runner answers are confirmed and reach a waiting runner at once (#3001),
andrig seat stopno longer suggestsrig downfor an adopted session
(#3006). They weren't re-checked for this release unless named here.
Credits
Thanks to @Aummadour, @Kayhusk, @Coder8124, @DeryFerd, @EZotoff, @hgreene624,
@cavalcanticampos, @ziadeh, @dajiaohuang and @billbenetti for merged
contributions. Thanks also for the reports behind these fixes: @jamesloosli
(#2879), @Kayhusk (#2880 and #2951), @CaptObvious (#2948 and
#3016), @alperta (#2917), @ziadeh (#2960) and @todd-dhango (#2984).