The capability map's 0.7.13 addition named rig network connect with its
flags. It now says what the release notes say: rig network connects one local
seat to a hub you already have, experimental and at your own risk, and the
daemon starts, sweeps and schedules the connector even with no binding, with
its migrations applied on upgrade.
The CHANGELOG section and what's new now disclose the queue-create slowdown
and memory reading, a notice left beside a late draft (#3076), an ordinary
send acting on an open /model picker, and the Codex hook review after an
upgrade, each as selected. They qualify the registration offer (5 of 6 fresh
installs) and the ask-back, mark #3029's behaviour as the change's own tests
with no fewer-asks claim, and name the Codex-installed-but-signed-out first
team. The opening drops the cut hash, the backup step gives its commands, the
MCP SDK is described as already in the package, rig network is one quiet
line, and the 0.7.12 limits are linked.
The TUI's unknown applies to the list, explorer and agent-detail status rows
for an explicit unknown from the daemon; screen motion, the screen fallback and
the topology graph are unchanged. Guidance cleanup removes redundant copies and
keeps distinct edits, and a write record decides whether an edit is kept on a
fresh start. The runner-answer note can ask for another answer. A stale pane
claim is reclaimed only by a handover launched into the seat's own session,
from a removed owner or an archived one whose session ended. A one-time park
wake is retried while its park is current and an attempt typed nothing.
The opening says rig daemon start tells the setup agent to offer to register
the person, and that a Claude seat waits when its usage-limit message states a
reset time. Plainer words for a failed wake's finding, a parked item's kept
wake, the custody-verified note and workflow spec reads. A marked place at the
end of each limits section for the items still to be filled in before
publication.
The marker moves to capability-delta-v0.7.13, and the verb count to 93
(`rig network`). Beside the verbs they belong to: a person's runner answer gets
a note back and the receiving agent knows what a terminal answer means;
`rig daemon start`'s registration offer and the operator-direct gap; a hosted
member's check-in status; `rig network connect` as experimental; stopping an
adopted session after `rig unclaim`, and the fresh launch that reopens the
server; a handover whose successor may be running; and usage-limit parking for
Claude seats.
The [0.7.13] CHANGELOG section above 0.7.12's: a runner's answer is confirmed
to the person, the receiving agent is told what a terminal answer means and how
to ask back, rig daemon start offers to register the person, a usage-limited
Claude seat waits for its stated reset, and fixes across delivery, handover,
the TUI and speed, with the experimental hub connector, the behaviour that
changed, the known limits and the credits.
What's new describes 0.7.13 for an agent on an upgraded install. 0.7.12's page
follows one heading level down, then 0.7.11's and 0.7.10's; 0.7.9's section is
dropped. The context-pack copy is the same file.
Set 0.7.13 in the root, cli, daemon, ui and acp packages and the lockfile,
the ACP launcher's @openrig/cli dependency and registry listing, and the
openrig plugin's four manifests, which carry the CLI's release version.
The install commands on the README, getting started and the quickstart name
v0.7.13: the rigs skill and the install script. Getting started and the
quickstart lead with the command for a new install and keep the matching
rig --version tag second, for an existing one.
The packaged-plugin baseline stays bound to published 0.7.12, and
openrig-core stays 0.1.29, above the published 0.1.28 for its changed hooks.
2026-11-12 11:31:20 +00:00
17 changed files with 1018 additions and 220 deletions
- **openrig-core is 0.1.29, and the `openrig` plugin now carries the CLI's
version, 0.7.13.** A Codex session kept running across the upgrade can ask
for hook approval until it's relaunched. ([#3034](https://github.com/mvschwarz/openrig/pull/3034), [#3064](https://github.com/mvschwarz/openrig/pull/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
the `rig seat decide-permission` command it names.
- 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](https://github.com/mvschwarz/openrig/pull/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`, or `check_in_on_request: true`): checking in, overdue, no
check-in yet, on request, or unknown. `rig roster show` and `find` print 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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/3003), [#3024](https://github.com/mvschwarz/openrig/pull/3024))
- After `rig unclaim`, the guidance for an adopted session says to end its
process and its tmux session, and `rig seat stop`'s help matches. A fresh
launch after `rig unclaim` ended the server's last session reopens the server.
- 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](https://github.com/mvschwarz/openrig/pull/2869), [#2987](https://github.com/mvschwarz/openrig/pull/2987), [#2995](https://github.com/mvschwarz/openrig/pull/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); a `custody-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](https://github.com/mvschwarz/openrig/pull/2948), [#3016](https://github.com/mvschwarz/openrig/pull/3016), [#3011](https://github.com/mvschwarz/openrig/pull/3011), [#3038](https://github.com/mvschwarz/openrig/pull/3038), [#3004](https://github.com/mvschwarz/openrig/pull/3004), [#2842](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2954), [#2879](https://github.com/mvschwarz/openrig/pull/2879), [#2951](https://github.com/mvschwarz/openrig/pull/2951), [#2880](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2857), [#3012](https://github.com/mvschwarz/openrig/pull/3012), [#3022](https://github.com/mvschwarz/openrig/pull/3022), [#2913](https://github.com/mvschwarz/openrig/pull/2913), [#2973](https://github.com/mvschwarz/openrig/pull/2973), [#2971](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2960), [#2986](https://github.com/mvschwarz/openrig/pull/2986), [#2999](https://github.com/mvschwarz/openrig/pull/2999))
- **Guidance and plugins:** guidance cleanup in a repository's `AGENTS.md` or
`CLAUDE.md` removes 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](https://github.com/mvschwarz/openrig/pull/3020), [#3025](https://github.com/mvschwarz/openrig/pull/3025), [#3021](https://github.com/mvschwarz/openrig/pull/3021), [#3064](https://github.com/mvschwarz/openrig/pull/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
- **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
with `rig launch`. ([#2964](https://github.com/mvschwarz/openrig/pull/2964), [#2984](https://github.com/mvschwarz/openrig/pull/2984), [#2991](https://github.com/mvschwarz/openrig/pull/2991), [#3002](https://github.com/mvschwarz/openrig/pull/3002), [#3031](https://github.com/mvschwarz/openrig/pull/3031))
### Experimental
- **`rig network`** connects 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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2917), [#3003](https://github.com/mvschwarz/openrig/pull/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 doctor` still checks actively.
- **Not in this release:** a Codex snapshot restore or `rig up --existing` can
write OpenRig's managed guidance into a tracked `AGENTS.md`, leaving the
worktree modified; check `git status` after 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 start` and `rig context` start the daemon without printing the offer
either. Register with `rig gateway human add`. While nobody is registered, a
later `rig daemon start` offers again, even after a no; nothing is registered
without your yes. ([#3028](https://github.com/mvschwarz/openrig/pull/3028), [#3041](https://github.com/mvschwarz/openrig/pull/3041) isn't in this release)
- **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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/3030), [#3001](https://github.com/mvschwarz/openrig/pull/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
- **`rig down`** keeps 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](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2980))
- **Custom blocker IDs** explain the wait, but their progress gives no event
wake; the timer remains. ([#2983](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/issues/2925)), and a held message's full envelope
can stay held; clearing a draft doesn't deliver it ([#2515](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/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 approve` or `rig 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](https://github.com/mvschwarz/openrig/pull/2850))
- **herdr-app views** are one-shot; following isn't claimed. **Pull relay** needs
a connector that implements pull. ([#2744](https://github.com/mvschwarz/openrig/pull/2744), [#2844](https://github.com/mvschwarz/openrig/pull/2844))
- **From 0.7.12:** [its known limits](https://github.com/mvschwarz/openrig/releases/tag/v0.7.12)
still apply, except that [#2970](https://github.com/mvschwarz/openrig/pull/2970) and [#2948](https://github.com/mvschwarz/openrig/pull/2948) are now in this release,
runner answers are confirmed and reach a waiting runner at once ([#3001](https://github.com/mvschwarz/openrig/pull/3001)),
and `rig seat stop` no longer suggests `rig down` for an adopted session
([#3006](https://github.com/mvschwarz/openrig/pull/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](https://github.com/mvschwarz/openrig/pull/2879)), @Kayhusk ([#2880](https://github.com/mvschwarz/openrig/pull/2880) and [#2951](https://github.com/mvschwarz/openrig/pull/2951)), @CaptObvious ([#2948](https://github.com/mvschwarz/openrig/pull/2948) and
[#3016](https://github.com/mvschwarz/openrig/pull/3016)), @alperta ([#2917](https://github.com/mvschwarz/openrig/pull/2917)), @ziadeh ([#2960](https://github.com/mvschwarz/openrig/pull/2960)) and @todd-dhango ([#2984](https://github.com/mvschwarz/openrig/pull/2984)).
## [0.7.12]
OpenRig 0.7.12 is a patch for people running their own agent teams, cut from
Then type `/rigs` in Claude Code, or `$rigs` in Codex, and say what you want built. The skill has your agent tell
@@ -68,11 +68,11 @@ Requires Node.js 22 or 24 and tmux, on macOS or Linux, and one working Claude Co
### Install it yourself
This runs OpenRig's install script from the `v0.7.11` release. It checks Node.js and npm, installs the latest published `@openrig/cli` with `npm install -g`, runs the Node.js and SQLite check, then runs `rig setup --dry-run` and `rig setup`. The first line prints that plan and changes nothing:
This runs OpenRig's install script from the `v0.7.13` release. It checks Node.js and npm, installs the latest published `@openrig/cli` with `npm install -g`, runs the Node.js and SQLite check, then runs `rig setup --dry-run` and `rig setup`. The first line prints that plan and changes nothing:
```bash
curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.7.11/scripts/install.sh | sh -s -- --dry-run
curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.7.11/scripts/install.sh | sh
curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.7.13/scripts/install.sh | sh -s -- --dry-run
curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.7.13/scripts/install.sh | sh
```
If the last step isn't ready, the installer reports `INSTALLED, SETUP NOT COMPLETE` and points to the details from `rig setup` above. Follow that output and any reported Fix, then rerun `rig setup`; the CLI does not need reinstalling. If the only remaining failures are provider sign-ins, sign in to each selected provider as below and continue.
- **Handover:** a handover whose successor launched but isn't ready says it may
be running. Look at the pane (`rig capture '<seat>'`) before another handover
or a fresh launch, either of which ends it. A handover also cleans up the
retiring occupant's own claims and jobs. ([#3003](https://github.com/mvschwarz/openrig/pull/3003), [#3024](https://github.com/mvschwarz/openrig/pull/3024))
- **Adopted sessions:** release one with `rig unclaim <session>`, then end its
process and its tmux session. Closing its viewing window only detaches it. A
fresh launch after that ended the server's last session reopens the server.
too) no longer hold a send, an unrecognised wake result reads unknown, and an
ordinary one-time park wake is kept and retried while its park is
current and the failed attempt typed nothing (an unknown effect needs checking;
repeating waits and usage-limit expiry keep their own lifecycle). ([#2948](https://github.com/mvschwarz/openrig/pull/2948), [#3016](https://github.com/mvschwarz/openrig/pull/3016), [#3011](https://github.com/mvschwarz/openrig/pull/3011), [#3038](https://github.com/mvschwarz/openrig/pull/3038))
- **The TUI:** for a quiet seat the daemon explicitly reads as unknown, the
list, explorer and agent-detail status rows show unknown. Screen motion still
shows active, a daemon that serves no activity keeps the screen fallback, and
the topology graph is unchanged. Feed times use `ui.timezone`. ([#3012](https://github.com/mvschwarz/openrig/pull/3012), [#3022](https://github.com/mvschwarz/openrig/pull/3022))
- **Experimental, at the person's own risk:** `rig network` connects one local
seat to a hub they already have. The connector uses the MCP SDK, which the
installed package already included in 0.7.12. The daemon starts it even with
- **0.7.12's limits below** still apply, except that [#2970](https://github.com/mvschwarz/openrig/pull/2970) and [#2948](https://github.com/mvschwarz/openrig/pull/2948)
are now in this release, runner answers are confirmed and reach a waiting
runner at once ([#3001](https://github.com/mvschwarz/openrig/pull/3001)), and `rig seat stop` no longer suggests `rig down`
for an adopted session ([#3006](https://github.com/mvschwarz/openrig/pull/3006)). 0.7.12's not-run list was for that release.
## What changed in OpenRig 0.7.12
This note is for an agent on an install that was just upgraded to 0.7.12.
OpenRig 0.7.12 routes a person's typed, clicked or qualified answers with the
question to the configured receiving agent or the kernel operator to decide.
Answers wait when no receiver is available. Setup's guidance asks the agent to
offer to register the person, which it didn't reliably do in testing. `rig down` stops
only terminals it can show belong to the seat. It adds five database
migrations. If you upgraded from 0.7.10 or earlier, also read "What changed in
OpenRig 0.7.11" below, and so on back. For the full capability map, read
`rig context get onboarding-width/public-what-you-can-do.md`. After the upgraded
daemon starts, `rig context get reference/whats-new.md` describes this version.
Without a running daemon, read the packaged `daemon/docs/reference/whats-new.md`.
### After the upgrade
- **Back up the database, then restart the daemon.** Five migrations run on the
daemon's first start: 155, 156 and 157 (queue erasure and its batches), 158
(queue inbox check-ins) and 159 (an index for handed-off rows). If
`$OPENRIG_DB` isn't backed up yet, copy that file (`rig config get db.path`
shows it) with the daemon stopped, then `rig daemon start`. Going back to
- 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; a direct decision uses the request's own command (`rig host approve`
or `rig host deny`, `rig seat decide-permission`). An ordinary close isn't
permission, and kept words aren't a default permit. ([#2923](https://github.com/mvschwarz/openrig/pull/2923))
- Pairing answers go to the receiving agent, and a person can decide directly in
the TUI's pairing settings. ([#2931](https://github.com/mvschwarz/openrig/pull/2931), [#2935](https://github.com/mvschwarz/openrig/pull/2935))
- A runner's permission answer goes to the receiving agent, which decides while
the runner waits, so a qualified answer ("only if it's the test file") is
read before anything acts. The answer is kept and an explicit decision works,
but the runner's confirmation updates to the person aren't written in this
release: no Feed confirmation, receiver-state notice or immediate wake. The
decision reaches the runner at its next read (up to about 21 seconds in
testing). Decide one directly with `rig seat decide-permission`. ([#2934](https://github.com/mvschwarz/openrig/pull/2934))
- **What to do:** design for an agent to read the person's answer with its
question and decide. If no receiver is available, say the answer is waiting;
don't describe it as read or decided. Pairing settings in the TUI also offer
the direct decision described above.
- **A chosen receiver** (`agents.operator_session`) in an explicit or auto
permission mode gets no OpenRig allowance for `rig host approve` or `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. When it needed to ask back in testing, the question
appeared in its own conversation, not in the Feed or Steering.
### Other changes to act on
- **Setup's guidance** asks the agent to offer to register the person; in
testing it didn't reliably make the offer (0 of 5 runs). Registering works
when the person asks for it (`rig gateway human add`): nothing is registered
without their yes, an existing default is kept, and no person is chosen
automatically. A team started from the person's own assistant fits their
logins, with a review before commit. ([#2924](https://github.com/mvschwarz/openrig/pull/2924), [#2905](https://github.com/mvschwarz/openrig/pull/2905))
- **Harnesses:** `protocol: pi-rpc`, launch wrappers in presets, and Pi
- **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](https://github.com/mvschwarz/openrig/pull/2934))
- **An already-running tmux server** keeps its old environment, daemon
credentials included, until it restarts. ([#2850](https://github.com/mvschwarz/openrig/pull/2850))
- **Delivery:** events are best effort, so a missing event isn't proof nothing
was sent. A footer row OpenRig doesn't recognize can still hold a delivery ([#2925](https://github.com/mvschwarz/openrig/issues/2925)),
and a held message's full envelope can stay held; clearing a draft doesn't
deliver it ([#2515](https://github.com/mvschwarz/openrig/pull/2515)). With unreadable input, `--dangerously-interact` pastes
with a warning and doesn't press Enter ([#2800](https://github.com/mvschwarz/openrig/pull/2800)).
- **Not run for this release** (not run, not passed): the two-seat Codex journey
with `AGENTS.md` restore; 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; native
checks of [#2786](https://github.com/mvschwarz/openrig/pull/2786), [#2799](https://github.com/mvschwarz/openrig/pull/2799), [#2807](https://github.com/mvschwarz/openrig/pull/2807) and [#2813](https://github.com/mvschwarz/openrig/pull/2813) ([#2947](https://github.com/mvschwarz/openrig/pull/2947) partly); a button-and-words
answer, a non-pairing ask with an explicit owner, Steering's Approve page, and
the answer and setup checks on a default model; `--wait-for-kernel` ([#2888](https://github.com/mvschwarz/openrig/pull/2888)),
[#2800](https://github.com/mvschwarz/openrig/pull/2800)'s installed effect, and [#2720](https://github.com/mvschwarz/openrig/issues/2720) beyond one platform. Don't tell a person
these work.
- **0.7.11's limits below** still apply, except Codex hook setup with smol-toml
1.9.x ([#2720](https://github.com/mvschwarz/openrig/issues/2720)), fixed by [#2804](https://github.com/mvschwarz/openrig/pull/2804).
## What changed in OpenRig 0.7.11
This note is for an agent on an install that was just upgraded to 0.7.11.
OpenRig 0.7.11 sends ordinary messages and work notices into a person's typed
draft by default instead of refusing them, lets a person reach the team from
their own coding agent (the `openrig` plugin) or an ACP app (`rig acp serve`),
holds a prepared managed compaction until the seat is idle, and clears a
restore that stopped at a prompt. On Linux, a daemon run as a systemd user
service keeps its seats when its unit restarts. It adds five database
migrations. On OpenShell 0.1.6 the worker's maintained cleanup now works, but
the worker still isn't end to end. If you upgraded
from 0.7.9 or earlier, also read "What changed in OpenRig 0.7.10" below, and
from 0.7.8 or earlier, "What changed in OpenRig 0.7.9" too. For the full
capability map, read `rig context get onboarding-width/public-what-you-can-do.md`.
After the upgraded daemon starts, `rig context get reference/whats-new.md`
describes this version. Without a running daemon, read the packaged
`daemon/docs/reference/whats-new.md`; `$OPENRIG_HOME/reference/whats-new.md` can
still be the previous copy until startup.
### After the upgrade
- **Back up the database, then restart the daemon.** Five migrations run on
the daemon's first start: 150 (node launch wrapper), 151 (Pi account
makes the team an agent in an app that launches a custom ACP agent, such as
Zed or T3 Code. Nothing runs until an app starts it, and it uses the daemon
`rig` uses. A question left unanswered in the app stays open in the TUI and
Slack. The `@openrig/acp` launcher is packed beside the CLI at the same
version. See `docs/reference/acp-agents.md`.
- **Assistants through a grant service** are experimental, unsupported and off
by default: they need your own internet-reachable `rig mcp serve --http
--grant-service <url>` and an outside grant service. A registered person can
answer the team's questions from one, and `--task-destination <member@rig>`
names where its tasks go (`docs/reference/hosted-members.md`).
- **The `relay` gateway connector** is off unless you add a relay binding. It
hands questions and updates to a bridge the operator runs on loopback;
"Accepted by bridge" isn't delivery (`docs/reference/gateway-relay.md`).
### OpenShell workers
On OpenShell 0.1.6 the maintained cleanup (`delete-owned`) now works for a
custom image, and recreate and an exact resume passed in our native run. A
restored guest still receives its startup text again, so strict recall after a
restore isn't met, and the worker isn't end to end. The CA fix holds on 0.1.6.
"Never grant the guest access to the daemon's main API
port (normally 7433)."
### Other changes to act on
- Denying or dropping a host pairing request in Steering now gives the requesting machine no access; in 0.7.9 and 0.7.10, that action could return the daemon access token. ([#2884](https://github.com/mvschwarz/openrig/pull/2884))
- **Pairing answers now reach the target's kernel operator.** On a 0.7.11 target with a receiving kernel operator, typed words and Approve or Deny choices in the TUI, Steering or Slack are replies for that agent to read. Receiving a reply neither grants nor denies access. The operator acts on clear intent with `rig host approve <code>` or `rig host deny <code>` and asks back when the answer is unclear. The commands also work from a plain terminal on the target; they use its operator bearer (`OPENRIG_AUTH_BEARER_TOKEN`, or `--bearer <token>`). ([#2900](https://github.com/mvschwarz/openrig/pull/2900))
- **An Approve click on an operator-owned request waits for the operator to act.** A stopped operator keeps ownership; the answer waits in its queue. A stopped or unknown running state is named with the terminal route, without claiming the answer was read. If there is no operator, it cannot receive answers, or OpenRig cannot determine one, the request names that case and uses the agent-free path: Approve and Deny decide directly, and replies lead to another ask rather than denial. File-only replies and the literal `[file reply]` have no words stored on the agent-free ask; they still do not deny it.
- **TUI answers use the daemon's operator bearer when configured.** Ordinary terminal calls keep their separate terminal credential. A missing or wrong action credential leaves the answer unrecorded and shows what to set; this does not weaken the daemon's authentication.
- **Receipt, clarification and outcome are separate steps.** Receipts, agent-free re-asks and outcomes inferred from clicks or closes need the requesting machine to keep polling. An explicit `rig host approve` or `rig host deny` attempts its outcome update directly. An expiry timer closes the ask even if polling stopped; an unanswered expired ask gets no further update. Requests and decisions live in daemon memory, so a restart drops an open request. Approval still must be collected before expiry. This target-side change does not change older targets.
- **Rows on another host:** `rig queue show`, `list`, `transitions`, `update`
and `block` take `--host <id>`; `claim` doesn't, since only the destination
seat on its own host claims. `--host` never follows `rig host select`.
- **A seat's unclaimed backlog:** a seat with no escalation route or delegation
parent gets one `unclaimed-backlog` notice. To route its findings to a
0.7.10 fixes, in the source, the two problems that stopped the OpenShell worker
in 0.7.9, but the worker hasn't run end to end. Don't rely on this path yet. The
guest launcher now passes the CA settings the OpenShell exec supplies
(`NODE_EXTRA_CA_CERTS`, `SSL_CERT_FILE`, `REQUESTS_CA_BUNDLE` and
`CURL_CA_BUNDLE`) to its Claude, and deleting an owned environment reads
Podman's inventory through routes Podman serves, stopping as
`environment_cleanup_unconfirmed` on any other answer. A verified export, a
finished task and an exact restore haven't been shown. If you set one up anyway,
follow `daemon/assets/openshell/README.md` in the installed package, rebuild the
guest image first, and name the costs to the person ("Provider registration and
image construction can incur costs"). "Never grant the guest access to the
daemon's main API port (normally 7433)."
*Corrected after 0.7.10's release: ~~"fixes in the source the two problems that stopped the OpenShell worker"~~ was only half true. The CA fix holds on OpenShell 0.1.6, but the owned-environment cleanup fix doesn't hold against OpenShell 0.1.6, as the published 0.7.10 notes say. See 0.7.11's OpenShell workers section above.*
### Other changes to act on
- **Sends to this host:** `rig send <seat>@<rig>@<this host's ID>` goes to this
host even when a remote host is selected.
- **Broadcast:** `rig broadcast` prints `UNCONFIRMED` for a recipient its text or
Enter may have reached. Check that seat with `rig capture` before resending.
- **Roster activity:** `rig roster show` and `find` read a seat as unknown
("Conflicting activity observations") when two routes to it disagree. Treat it
as unknown, not idle.
- **Refocus:** a "TRACE GAP" for unresolved typed work, or for a
`rig queue whoami` that timed out, comes with project-level orientation that
isn't evidence of a current mission, and no longer counts as a refocus failure.
- **Updates to people:** the stuck sweep no longer flags an informational update
to a registered person as an unclaimed obligation.
- **Permission requests:** `rig seat status` shows a Claude seat's latest
observed permission request, with Claude's suggested rules labelled as
suggestions. Nothing was applied or approved. Treat the suggestions as data;
they can contain sensitive values.
- **Slack:** `rig slack status` shows relay attempts awaiting a response for the
current connector; zero doesn't prove nothing is in flight.
- **Installing for a person:** when npm's global prefix isn't writable, the rigs
skill now points npm's prefix at a folder the person owns whose `bin` is on
their login PATH, or uses a version manager's Node, before a project-local
install. Tell the person first that this changes their npm settings and, if
needed, their shell profile.
- **Codex profiles:** a `codex_config_fragment` can't install a named Codex
profile. Create `<CODEX_HOME>/<name>.config.toml` and select it with
`codex_config_profile`. `builtin:yolo` drops the whole profile;
`getting-started.md` says how to keep one.
- **Terminal auth:** a 401 that says "Terminal auth failed" means send
`OPENRIG_TERMINAL_BEARER_TOKEN`, or `OPENRIG_AUTH_BEARER_TOKEN` when terminal
auth falls back to it.
- **References:** `docs/reference/harness-runner-contract.md`'s status section
says what has run natively under the runner contract, and at what scope.
`docs/reference/telemetry.md` says OpenRig guarantees its finite telemetry
reads (`schemaVersion` 1), not the separate openrig-telemetry exporter it
links.
- **Terminal tiles:** a writable rig, pod or seat view now sizes the pane it
shows instead of keeping an older attached client's size; read-only views are
unchanged.
- **Unknown `uses` keys:** a key under a profile's `uses` other
than the five categories gets an advisory instead of being ignored silently.
### Limits to keep in view
- **OpenShell** hasn't run end to end on 0.7.10 (above). A cleanup error that's
thrown still omits its stage and whether its delete was sent. A
same-generation reconciled launch opens no viewer, so run
slack:<connectorRef>:<secretsRef>:<channelId>`** — a Slack shared channel as one participant,
`<id>@external` (Slack only). Anyone writing there reaches the team, registered or not. Each row
@@ -1402,7 +1415,8 @@ your circumstances is configuration, and the ones that are not, another agent ca
conversation it is in the middle of. **`provider signals` reports anomalies rather than a
listing** — unbound seats, accounts shared across several seats. A Codex seat showing its
usage-limit banner reads activity `unknown` with reason `usage_limit`, and keeps it while its
screen redraws; `provider signals` can show a provider-event signal for that seat's account that
screen redraws (a banner with a curly apostrophe included); a Claude seat whose usage-limit message
states a reset time is parked until then, instead of being retried every few minutes; `provider signals` can show a provider-event signal for that seat's account that
allows a switch decision. With `provider.usage_windows` on (off by default), `rig provider status`
shows Codex's windows and Claude's 5-hour and weekly windows from the seats' status lines, each
seat's configured account, and with `--all-hosts` or `--hosts <ids>` every registered machine's
@@ -1467,7 +1481,11 @@ your circumstances is configuration, and the ones that are not, another agent ca
(empty, the default, means every signed-in one). `--router-line yes|no` decides whether OpenRig
adds its one line to shared guidance files (`skills.router_line.enabled`).
Setup offers to register the person when none is registered, and a team started from the
person's own assistant fits their own logins, with a review before anything is committed.
person's own assistant fits their own logins, with a review before anything is committed. Since
0.7.13, `rig daemon start` ends with that offer, where the setup agent reads it, when the person
registry can be read and holds nobody. A person who talks to the kernel operator first, with no
other agent setting OpenRig up, isn't offered it yet; `rig gateway human add` always works, and
nobody is registered without their yes.
- **`rig usage series`** — what a seat's token curve has looked like over time: climbing steadily,
reset, or stopped reporting entirely. The last one is a signal, not a gap.
- **`rig usage top`** — which of this machine's seats used the most tokens over a window (`--window
@@ -1564,6 +1582,9 @@ your circumstances is configuration, and the ones that are not, another agent ca
with secret names, never values): OpenRig then POSTs a pointer to the row when work lands, and a
2xx records only that the ring was accepted, not that anything woke. When work waits for a
member nothing can wake, or a rung member doesn't claim it in time, its person is told.
A hosted member's roster entry shows whether it's checking in: its expected cadence and its last
check-in, read as checking in, overdue, not yet checked in or checking in on request, and unknown
when that can't be read. It's a status, never a gate on delivery.
**Internet-facing hosted members are experimental, unsupported, off by default and at your
own risk.** Local assistants can connect locally. Internet access needs your own TLS tunnel or
proxy and a narrowly scoped, revocable token; see `reference/hosted-members.md`. Task terminal
@@ -1653,6 +1674,6 @@ deliberate writing.
**`rig --help`**, then `rig <verb> --help`.
Ninety-two verbs ship, and this page named most of them once. **You will not remember which — you
Ninety-three verbs ship, and this page named most of them once. **You will not remember which — you
are meant to remember only that the list is long enough to be worth reading before you build
anything.** The question is never *how do I write this*; it is **does this already exist**.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dev60-review