What's new

Node reads (rig ps --nodes, the TUI, several agents at once) take turns, one step at a time. In the change's own tests, health checks and queue reads were no longer held behind a whole burst. A comparison under load didn't attribute a gain to this change: health checks and queue reads were faster for the release as a whole, rig ps --nodes showed no change, and sends were inconclusive.

#3101Link

Bounded queue listings over retained history use indexes for their ordering and for live and archived owner notifications.

#3090Link

Codex seats re-checked in one readiness poll share process listings where each seat's observation order and the 2 s freshness allow; each keeps its own later observation and its own fallback.

#3061 · thanks @KayhuskLink

New tmux servers raise their soft open-file limit to 8,192 or the hard limit where they can, keeping an already higher limit. This makes descriptor exhaustion less likely as panes and viewers add up; servers already running keep their limits.

#3070Link

A delegation parent gets one standing notice per child seat for unclaimed rows, not one per row, and held work gets its notice back when its typing hold clears.

#3049, #3082 · thanks @billbenettiLink

An assistant connected over MCP reaches a seat by its plain name, stored under the seat's actual session; an unknown name, or one several seats match, says so.

This is for hosted agents connected through a grant service (experimental); seats OpenRig launches behave as before.

#3088Link

Connected assistants appear, with their check-in, in rig ps, rig_team and the TUI's tables, and their person sees plain tool titles.

#3057, #3058, #3092Link

A team your agent hands work to knows how to ask you a question, and your answer wakes it. A click on an ask with several questions records that choice; the ask stays open until the last one.

#3059, #3045Link

A skill-only edition of the openrig plugin, for Claude's plugin directory, follows handed-on work and keeps its reply route.

#3056, #3075Link

When the readable person registry holds nobody, rig daemon start and rig gateway participants tell the setup agent to offer registration. The kernel operator is taught to include that offer in its greeting and register only on your yes.

#3041, #3071Link

A pairing request's description of itself is quoted wherever it's shown.

#3067Link

An ordinary send is refused as needing input while an open Claude Code or Codex /model picker is positively identified; nothing is typed. Close the picker before trying to deliver the message. This is shown by the change's own tests; it hasn't yet been checked with the real Claude Code and Codex programs on this release.

#3083Link

On a resume of a Codex seat's own conversation in a rig with pods, including rig up --existing, OpenRig avoids adding missing guidance blocks to the repository's tracked AGENTS.md when Codex is 0.164.0 or later, no guidance file or developer instructions are configured, and the configuration and block sources can be read.

#3039Link

With recovery.auto_drive_provider_prompts on, Claude Code's gated-grants trust check is never answered for you, and the plain trust prompt is answered "Yes".

#3073 · thanks @billbenettiLink

rig broadcast prints a held recipient as retained, not sent.

#3054Link

Account erasure also removes OpenRig's own wakes and notices for that account's seats.

#3089Link

A snapshot without sessions returns its invalid_snapshot_data blocker instead of throwing a TypeError; the restore still stops there. A retried no-launch import recovers the original rig by its operation ID.

#3069, #3042 · thanks @cavalcanticampos, @KayhuskLink

A rebuilt briefing limits optional superseded recap paths to the newest three by default when one folder covers that history; the current recap and all artifact records remain. Other layouts keep the full list, and output.rebuild_recaps set to 0 lists all paths.

#3055 · thanks @KayhuskLink

rig compact --state names the input check that stopped a managed compaction, and the TUI's graph shows a seat the daemon reads as unknown as unknown.

#3053, #3046Link

Setting a context-pressure threshold explains when an environment override inverts the pair, and rig workflow validate warns that harness pins aren't checked against seats.

#2567, #3102 · thanks @Totopo27, @cavalcanticamposLink

The config browser's entries say each setting's type, choices, range, format and write route.

#3050 · thanks @w4rc0nLink

rig network is experimental, unsupported and at your own risk. Its connector isn't inert: the daemon starts it, sweeps leftover credential folders and schedules local rounds even with no binding.

#3007, #3084Link

A grant service can hold back only new work under its fair-use limit, and an app can read what needs a person, and the answers to it, by link.

#3048, #3008Link

Node reads: a nodes response is no longer one snapshot across its steps, and in a burst each nodes response comes later: about 43 ms against 21 ms median in a 24-request burst. One very large rig is still one step.

#3101Link

An assistant naming a seat now hears three errors: destination_ambiguous (several seats match; the candidates are listed), destination_not_found (no seat it can reach has that name) and destination_unchecked (the team couldn't be read; try again).

#3088Link

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.

#3023Link

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 · thanks @billbenettiLink

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.

#2996, #3006, #3014, #3009Link

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 · thanks @KayhuskLink

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, #3019Link

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, #2984, #2991, #3002, #3031 · thanks @ziadeh, @dajiaohuang · reported by @todd-dhangoLink

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, #3016, #3011, #3038, #3004, #2842 · thanks @EZotoff · reported by @CaptObviousLink

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 · thanks @Kayhusk, @Coder8124 · reported by @jamesloosliLink

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 · thanks @hgreene624, @Kayhusk, @DeryFerdLink

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 · thanks @Aummadour · reported by @ziadehLink

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.

#2993Link

A runner's answer is confirmed to you. Through 0.7.12 no note came back, and the runner waited for its next read.

#3001Link

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 · thanks @cavalcanticampos, @billbenetti · reported by @alpertaLink

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.

#2979 · thanks @AummadourLink

rig package install leaves 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).

#3020Link

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, #2905Link

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 approve or rig host deny for a pairing request, rig seat decide-permission for a runner's request. Closing an ask isn't permission, and words that were kept aren't a default permit.

#2923Link

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, #2935Link

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, #2966Link

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=pull in the relay secrets file. Push stays the default. A person's gateway binding can be unset.

#2844, #2812 · thanks @w4rc0nLink

rig terminal open <view> --provider herdr-app opens a Rig view inside the herdr-app desktop window.

#2744, #2956, #2981 · thanks @w4rc0nLink

Queue content can be erased for closed-work retention and account deletion, and a retried create can't bring erased work back.

#2837, #2843Link

Each send records what's known about its delivery in one transport.delivery_evidence event: what was admitted, what reached the input, what the screen check showed, and for which occupant.

#2937, #2943Link

rig queue create advises 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 show names a handed-off row's successor, and a custom blocker ID explains the wait.

#2901, #2902, #2867, #2872, #2874, #2983 · thanks @Aummadour, @dajiaohuangLink

Every seat's managed guidance points to its skills, help and project context. rig seat status shows 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, #2876Link

Speed: queue listings, rig queue show and rig parked stop re-reading each item; the stuck sweep yields by elapsed time; Markdown section ends are found in one pass.

#2825, #2926, #2833 · thanks @billbenetti, @oodadoudouLink

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 · thanks @billbenetti, @KM199 · reported by @CaptObviousLink

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 · thanks @KM199 · reported by @djuntgenLink

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 start archives 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 · thanks @ziadeh · reported by @KayhuskLink

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; a handoff doesn't change an escalation's owner; findings route to the seat's own fallback; a park on an outside condition with no wake says so; rig workflow validate is read-only.

#2864, #2957, #2790, #2824, #2946, #2865, #2851, #2852, #2817, #2763 · thanks @seanmcn, @billbenetti · reported by @todd-dhangoLink

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 · thanks @seanmcnLink

CLI and config: rig context recap-write writes where every reader looks; config accepts two keys the daemon already resolves; rig whoami says the team is still being built during rig 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 · thanks @DeryFerd, @Vaishnavi220506 · reported by @nassersala, @pr0xc3nt4ur1Link

Terminals: a Herdr grid whose blank filler cells have no label is confirmed, instead of reading every seat unconfirmed.

#2849 · reported by @pr0xc3nt4ur1Link

rig down leaves terminals it can't show belong to the seat; see Before you upgrade.

#2962Link

A daemon start reservation left after a reboot is archived by rig daemon start; don't clear it by hand.

#2915 · thanks @ziadehLink

A draft only the input box shows is caught by one read before pasting.

#2653Link

Claude seats showing a statusLine or the background task panel read as a normal composer under the draft-aware guard.

#2703 · thanks @billbenettiLink

A full held-message quota no longer drops a sender's later messages, and seats stopped while they owe work don't get a burst of undeliverable notices at each daemon start.

#2701, #2620 · thanks @billbenettiLink

on_restore: follow_source on a skill refreshes it from its source when a seat is restored; keep_saved stays the default.

#2626 · thanks @seanmcnLink

The final /compact allows for the preparation's own fresh activity (23 seconds, against 9), so a seat that's already idle gets /compact instead of a refusal.

#2764Link

A restore stopped at a prompt, such as Claude's resume selection, clears itself once the seat runs the conversation it was restoring.

#2711, #2674 · thanks @ziadehLink

A work notice refused at a prompt no longer goes in right after "Compacted" while the compaction still owes its restore request.

#2666 · thanks @Nikhi00718Link

A Codex helper inside a Claude seat no longer becomes the seat's resume token; a Claude rebuild handover checks its priming packet; restoring activity hooks finds the agent's own source.

#2740, #2650, #2617 · thanks @AummadourLink

The @openrig/acp launcher runs the matching @openrig/cli's rig acp serve for the ACP registry's npx launch, released at the same version.

#2655, #2715Link

Assistants connected through a grant service can list and answer the team's questions as a registered person, and --task-destination names the receiver for new tasks.

#2735, #2638, #2750Link

The relay gateway connector sends questions, updates and notices to an operator-owned bridge over loopback HTTP and takes replies back. The bridge is yours.

#2624 · thanks @smotaLink

The web UI's For You feed answers a local ask's questions on its card.

#2612 · thanks @w4rc0nLink

rig queue show, list, transitions, update and block take --host <id>; cross-host handoffs that override a claim notify the claimer.

#2678, #2734, #2621 · thanks @billbenettiLink

An openrig.code-result/v1 manifest gives rig queue artifact the commit pair to diff.

#2659Link

Workflows keep their own spec and root objective, rig workflow unregister removes versions, and trace --full returns the whole trail.

#2696, #2738, #2676, #2667 · thanks @billbenettiLink

One backlog notice replaces a finding per task for a seat that reads without claiming; claims read working while a Claude owner has a live background shell or a managed restore is owed.

#2752, #2675 · thanks @billbenettiLink

A helper harness inside a seat no longer reports its turns as the seat's; refocus traces projects outside workspace.root.

#2743, #2664, #2717, #2619, #2207 · thanks @MohsintlLink

rig provider switch --seat <pi seat> --to-account <name> --account-home <dir> --reason "<why>" moves a Pi seat to another account through a confirmed successor (--dry-run shows the plan); in our native run the successor started but the switch wasn't completed, so a completed switch is untested. A Pi seat whose spec declares its account home starts and resumes again.

#2630, #2782 · thanks @seanmcnLink

A Claude seat launched with --settings JSON written with spaces can be verified again, and a Claude launcher script that execs the native installer's symlink becomes ready, with --no-chrome recognised; in our test, 0.7.10 also became ready under the same chain, so this isn't a demonstrated fix.

#2665, #2751 · thanks @Nikhi00718Link

launch_wrapper works for local Claude Code, Pi and Codex seats, and a wrapped seat never starts unwrapped.

#2746, #2609 · thanks @smotaLink

Claude seats that load openrig-core themselves stop loading its skills twice.

#2660Link

Also: rig attach --self outside tmux, rig host pair --timeout, rig config set naming a masking variable, daemon start and stop treating a blocked probe as unknown.

#2640, #2641, #2692, #2547, #2502, #2643 · thanks @seanmcn, @dajiaohuangLink

Answers to a pairing request now reach the target's kernel operator. When the target has an operator that can receive them, typed words and Approve or Deny choices in the TUI, Steering or Slack go to that agent as replies, and receiving one 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. Both commands also work from a plain terminal on the target, using its operator bearer (OPENRIG_AUTH_BEARER_TOKEN, or --bearer <token>). An Approve click on a request the operator owns waits for the operator to act; a stopped operator keeps the request, and the answer waits in its queue.

Checked on this package: real Slack with a real operator agent in one run (a button or a typed yes approved, a no denied, and a qualified reply got a clarifying question before the refusal denied it); the real TUI without a model (answer credentials, typed answers asked again with no operator, plain-terminal approve and deny, and expiry); and 29 of 29 contained cases with synthetic credentials. Not run: an agent reading answers given in the TUI, Slack thread replies beyond the tested path, and Steering in a browser.

#2900Link

With no operator, one that can't receive answers, or one OpenRig can't determine, the request says so: Approve and Deny decide directly, and a typed reply gets another ask instead of a denial (the no-operator case was checked; the other two come from the source).

#2900Link

TUI answers use the daemon's operator bearer when one is configured; a missing or wrong one leaves the answer unrecorded and says what to set. Ordinary terminal calls keep their own credential.

#2900Link

Denying or dropping a host pairing request in Steering now gives the requesting machine no access. The problem, that action returning the daemon access token, was found in the 0.7.9 and 0.7.10 source and reproduced with synthetic credentials on an earlier 0.7.11 build.

#2884Link

Herdr follow views work on macOS too (protocol 22).

#2663, #2706Link

Writable tiles reflow with the screen: they attach as in 0.7.10, so the screen in use sizes the seat and text reflows on resize, and once attached tmux handles typing and paste directly. Read-only tiles keep showing the seat without attaching, typing into it or resizing it. Fixed web geometry is opt-in (terminal.fixed_geometry, off by default); that browser option wasn't exercised in our checks. Checked in one run in real Herdr 0.9.5 on tmux 3.4 (reflow while viewing, typing and paste once attached, and a tmux window fixed by hand at 80x24), with typing and paste also checked on tmux 3.4, 3.3a and 3.6; phone-size screens and tmux 3.3a weren't run in Herdr.

#2868, #2757Link

Closing the herdr-core terminal that started OpenRig no longer ends the daemon or its seats. After merging, @w4rc0n ran a real close with herdr-app 0.1.13 in an isolated Linux sandbox: without the change the daemon, tmux server and seat ended, and with it they kept running. That sandbox had no systemd --user, so herdr-core's service-unit path wasn't run, and a tmux server started inside the terminal before the daemon still ends with it.

#2737 · thanks @w4rc0nLink

Terminal snapshots keep colours, a reattach during a broker teardown works, and rig doctor says why tmux control mode is off.

#2654, #2671, #2633, #2707 · thanks @twotnguyen, @seanmcnLink

The stuck sweep batches its reads: on a copy of a busy 340 MB database, a pass went from about 11 s to about 5 s and the longest stall from about 10 s to 0.57 s.

#2649 · thanks @billbenettiLink

view.changed events are no longer stored, and opt-in retention.events_days prunes eight history-only event types.

#2695, #2699 · thanks @billbenettiLink

The web UI loads the newest 100 events; daemon.seat_poll_interval_ms trades activity freshness for daemon CPU.

#2704, #2688, #2636, #2690, #2713 · thanks @billbenetti, @seanmcn, @AummadourLink

Docs and tests. Daemon HTTP clients and bearer tokens, the 0.7.10 capability map, a neutral TUI demo snapshot, a web UI editor timer, and test and CI fixes.

#2652, #2736, #2724, #2689, #2753, #2681, #2685, #2673, #2628 · thanks @dajiaohuang, @seanmcnLink

Sends and work notices that were refused with prompt_draft now go through by default, joined to the person's draft. rig config set transport.draft_delivery refuse restores the refusal from the next send, and under refuse a draft only the input box shows now refuses too.

#2645, #2653Link

A Pi seat with an absolute PI_CODING_AGENT_DIR uses it as its account home; no auth.json, no launch.

#2630 · thanks @seanmcnLink

/api/events no longer emits view.changed.

#2695 · thanks @billbenettiLink

The stuck sweep files one backlog notice where it filed one per task.

#2752Link

A prepared managed compaction stays waiting, and a manual rig compact over it reads already_in_progress.

#2698, #2716 · thanks @billbenettiLink

The daemon and seats no longer inherit HC_SCOPE, HC_TERMINAL_ID or HC_TERMINAL_SOCKET.

#2737 · thanks @w4rc0nLink

Read-only terminal tiles show the seat without attaching; writable tiles attach as in 0.7.10, and detaching ends that viewer while the agent keeps running.

#2757, #2868Link

On a target with a kernel operator that can receive answers, an answer to a host pairing request no longer decides it: the operator decides with rig host approve <code> or rig host deny <code>.

#2900Link

A stale record naming a reused tmux pane no longer stops a send from leaving the mode.

#2644Link

Writable views size the pane they show.

#2614Link

Herdr views kept from 0.7.5 through 0.7.9 keep working after upgrading (Linux Herdr 0.9.5 / protocol 22): when only OpenRig's tile script changed, a viewer stays confirmed and a follow view goes on adding and closing tiles. A kept viewer that's already running keeps its earlier sizing for as long as it runs, its own re-attaches included. With a live Herdr after upgrading from 0.7.9, a kept viewer and a follow view's join worked. Closing a tile when a seat leaves wasn't confirmed. It follows @natefaerber's approach in #2467.

#2634Link

rig seat status shows a Claude seat's latest permission request, with suggested rules labelled. Nothing is applied or approved.

#2562 · thanks @AummadourLink

Routing and status: a send to <seat>@<rig>@<this host's ID> stays local; rig broadcast says UNCONFIRMED, not FAILED, for an uncertain recipient; refusals for seats handed over before 0.7.9 say why; rig roster reads conflicting activity as unknown; set-runtime finds pod recaps.

#2600, #2572, #2574, #2593 · thanks @Vaishnavi220506, @dajiaohuang, @Nikhila-Dhevi-RLink

Refocus names a trace gap instead of failing.

#2582, #2587 · thanks @dajiaohuang, @billbenettiLink

The stuck sweep stops filing informational updates to people as unclaimed work.

#2586 · thanks @AummadourLink

rig slack status counts cross-host relays in flight.

#2569 · thanks @dajiaohuangLink

Plain rig works in managed Codex seats however OpenRig was installed, with a Codex that supports allow_login_shell: tool commands now run in a non-login shell, and rig config set launch.codex_login_shell true defers to Codex's own setting.

#2613Link

Errors are clearer: a refused terminal token says "Terminal auth failed"; the TUI shows the daemon's launch refusal; rig doctor gives up on a silent listener after 2 seconds.

#2577, #2556, #2564 · thanks @Aummadour, @dajiaohuangLink

The execution view reads the review registry once per request. Queue listings build one recovery index instead of a scan per listed task. The event drain reads at most 500 rows at a time. On a test fixture, full listings were about 63% faster with the same output. The listing and drain changes are unmeasured on a live install.

#2578, #2588, #2610 · thanks @billbenettiLink

The guest passes the exec's CA settings to Claude, so API calls stop failing with SELF_SIGNED_CERT_IN_CHAIN. TLS checks stay on. With OpenShell 0.1.6 the guest now authenticates, does useful work, makes a verified export and completes its task.

#2602Link

Owned-environment deletes read Podman's inventory, and an unconfirmed cleanup stops as environment_cleanup_unconfirmed. The maintained cleanup still fails against OpenShell 0.1.6 (see Known issues).

#2603Link

Docs and tests. Codex named profiles, openrig-core skill loading, what the runner contract has run, telemetry's guarantee beside the separate, untested openrig-telemetry exporter, and a real-tmux test that waits for the prompt.

#2604, #2584, #2592, #2595, #2589, #2559 · thanks @dajiaohuang, @smotaLink

A held post-compaction step goes in over an unreadable box, so an unrecognised draft may receive the restore text.

Link

Sends leave any tmux mode a person has open.

Link

rig up can print advisory warnings.

Link

Managed Codex seats run tool commands in a non-login shell, so login- or rc-only setup, shell functions and aliases may be missing, and a model request for login: true gets Codex's refusal.

Link

Experimental and unsupported. Off by default. Use at your own risk. This path needs a grant service that you supply and run; ordinary use of OpenRig doesn't need one. With rig mcp serve --http --grant-service <url>, a connected assistant can now claim, update and park the rows addressed to its own seat, and see its team with rig_team, within the scope its existing tools have. Serving MCP over HTTP behind your own tunnel "is like opening a port in your firewall." See docs/reference/hosted-members.md.

#2384Link

New daemon reads, two of them by @dajiaohuang: people and the default person, a person's open updates without Slack, a rig's messages in one request, and Slack channels and people without the client holding the bot token. An opt-in decisionRevision lets a client settle exactly the decision its person reviewed. docs/reference/daemon-http-clients.md covers them. The people, updates and messages reads pass their route tests, but no real client used them in our release testing.

#2495, #2497, #2496, #2501, #2448, #2490 · thanks @dajiaohuangLink

Options and views: specs.builtins_visible: false hides built-in specs; plugin_channels passes a Claude member's plugin channels to --channels (by @Aschenbath, carrying on @todie's fork work), warns beside claude_mcp: none, and hasn't been run with a real channel plugin; rig context add <url> installs into a new nested name; TUI and web UI display fixes.

thanks @Aschenbath, @todieLink

Status and receipts: idle Claude and busy Codex seats read correctly in more layouts; stale window samples expire, so a seat whose pane can't be read reads unknown rather than its last verdict; uncertain sends read unconfirmed or indeterminate instead of delivered, lost or failed.

Link

Guidance and handover: an edited culture or startup file reaches the next start, while your own edit to a managed block is kept; shared CLAUDE.md and AGENTS.md files stop growing; handover successors get their guidance and a list of their startup files; several Claude rebuild and resume failures are repaired.

Link

Asks: in a shared workspace, any registered person can settle another's ask and the first answer wins; a person may have no connector binding; Slack records a click on a re-parked ask and marks asks handled.

Link

Install and hosts: the upgrade skill backs up without the sqlite3 CLI when Node has node:sqlite; preflight warns when a Codex seat's login shell can't find rig; rig host ls reads your ssh config with ssh -G, which runs any Match exec command in it; rig doctor no longer hangs on a port held by a listener that never replies; a scoped launch on tmux 3.4 keeps its default command.

Link

The OpenShell worker still doesn't work in 0.7.9. Don't rely on this path. 0.7.9 repairs the layer that stopped it in 0.7.8: in our release testing the guest's agent now starts and reaches its first input. Startup reaches the guest through a hash-checked first-input file, and nothing is typed through the host viewer; the case where the viewer exits wasn't run in our release testing. Readiness checks the guest's own execution, and a failed owned delete reports the stage that failed. Our release testing on 0.7.9 then found two more problems: The worker can't reach its model. The guest's Claude starts, but every API call fails with SELF_SIGNED_CERT_IN_CHAIN. The guest launcher builds a clean environment and leaves out the CA settings the OpenShell exec supplies (NODE_EXTRA_CA_CERTS, SSL_CERT_FILE, REQUESTS_CA_BUNDLE and CURL_CA_BUNDLE). Deleting an owned environment doesn't run. Its inventory step misreads a "Not Found" reply, so the delete is never sent and the owned resources stay. In our test they were removed with the vendor's own cleanup. Attached resources were kept, as intended, and the worker stopped cleanly. With the four CA settings passed through by hand, a worker did useful work; a verified export, an exact restore and a finished task weren't shown. Fixes for both problems are on main (#2602, #2603). They aren't in 0.7.9 and haven't been run end to end.

#2418, #2404Link

Stream intake is on by default (see Before you upgrade).

Link

Fresh Pi seats, and fresh Codex seats on 0.164.0 or later, get OpenRig's guidance outside the repository AGENTS.md: Pi in its own agent folder (unless that file or folder is a link), Codex as launch developer instructions. Codex still uses the repository file for a resume, fork, restore or handover successor, an older or unknown version, or a config layer that sets developer_instructions or can't be read. If only your shell startup sets CODEX_HOME, OpenRig reads ~/.codex, so a developer_instructions in your home is replaced for that session; declare the same absolute path as CODEX_HOME in the member's or rig's env: to have it checked.

#2432, #2441, #2443Link

rig down removes OpenRig's own additions from a working folder once no live seat uses them.

#2387Link

After upgrading, the Slack connector edits asks that ended earlier to show they were handled, at Slack's edit rate: about an hour for 450 asks. rig slack status shows pending edits.

#2472Link

A later answer to a settled ask gets 409 qitem_already_terminal and records nothing.

#2386Link

rig send --verify reports unconfirmed and exits 1, not delivered, when it can't see what its Enter did.

#2509 · thanks @dajiaohuangLink

rig export with no -o writes rig-export.yaml beside an existing rig.yaml instead of replacing it.

#2356 · thanks @Nikhi00718Link

rig workspace validate exits 1 for malformed optional frontmatter.

#2396 · thanks @oodadoudouLink

An active rig name that matches more than one rig makes rig env down, status and logs list the matching rig IDs and stop, and rig doctor --spec report conformance as unknown, instead of using the first match.

#2548, #2550 · thanks @dajiaohuangLink

New default kernels start in <workspace.root>/kernel. Existing kernels stay where they are; docs/reference/agent-startup-guide.md describes the optional move.

#2402Link

A runner conformance check: node docs/reference/runner-conformance/check-runner.mjs --runner '<runner command with {agent}>' --name <harness>. It covers the answered path, and needs Node and tmux but no daemon, model, credentials or network.

#2303, #2306Link

An example runner for DeepSeek Harness (dsh), with its preset, is under docs/reference/community-harness-examples/dsh/. OpenRig doesn't install it.

#2305Link

A seat activity grant lets a runner outside the host's hook setup report activity for one seat and launch, without the install-wide hook token.

#2295Link

0.7.8 includes rig environment (setup, create, attach) and a reference for binding a seat to an NVIDIA OpenShell sandbox (daemon/assets/openshell/README.md). In our release testing the worker never became usable: after the sandbox was created and the native process started, rig environment connect failed when its check timed out after 5 seconds, so no team work ran. Don't rely on this path in 0.7.8. The packaged CHANGELOG and What's new describe it as working; this release body replaces them on that point.

#2296, #2300, #2378Link

Hosts and setup: rig host edit and rig host remove; a warning when another OS user's daemon holds the port; rig daemon status shows a pending start.

#2310, #2346, #2302, #2348 · thanks @DeryFerd, @Vaishnavi220506Link

Wakes: OPENRIG_WAKE_SUSPEND matches destinations with a colon; prompt escalations stay deliverable without a reachable person; reminders stop at a full quota; human@kernel raises no false finding; OpenRig's own Codex hooks are trusted when no choice is recorded; refusals name their fix.

#2353, #2343, #2281, #2286, #2294, #2290, #2284, #2280, #2273, #2202 · thanks @dajiaohuangLink

Also: MCP text is cut between whole characters; an ACP cancel survives a failed note; long transcript lines read faster; there are Pi and kernel dashboard recovery guides.

#2268, #2262, #2274, #2186, #2275 · thanks @Nikhi00718, @Vaishnavi220506, @oodadoudou, @dajiaohuangLink

A runner following section 7 gets answers or permits, not refusals. --deny keeps a seat refusing.

Link

On tmux older than 3.7c, OPENRIG_TMUX_CONTROL=1 uses spawned clients instead of a control client.

Link

A failed handover no longer moves the seat's resume target to the new, unprimed conversation while the seat keeps its previous occupant.

#2354Link

New slice views start with four automatic tiles; --max-tiles changes that. A known empty slice keeps following and fills again. An incomplete read keeps the previous viewers, and missing or ambiguous slices are named, never shown as an empty team. Pins, drafts, unknown input and focus still protect a departed viewer, and closing a viewer never stops its agent.

Link

When a slice's folder name repeats across missions, tag its work with the slice's unique ID (or add --mission). A row tagged only with the shared name can't be placed, so the view reads incomplete until it is.

#2261Link

Slice following targets Linux Herdr 0.9.5 / protocol 22. Following a whole mission isn't in this release.

Link

An owner whose join was refused before any pane split now joins on a later refresh, and a viewer that hasn't attached yet can carry on.

#2271Link

Named Herdr sessions use their configured endpoint throughout, and the TUI's terminal action opens the agent, pod or rig in view.

#2205, #2232Link

A Claude seat can switch between subscription and API key on the same conversation (--to-account api --api-key-file <file>, back with --to-account plan --token-file <file>). In-flight work is interrupted. The API-key path is not qualified yet, so check the resulting account and conversation. A new Claude member can name its own token file in its spec with claude_token.

#2191, #2246 · thanks @seanmcnLink

Managed seats inherit the daemon's SSH agent for git over SSH.

#2222Link

Community-harness presets can opt into runner: true (with launch_result: true) so the seat's activity follows its runner, and passes_model: true to receive the declared model as OPENRIG_MODEL. That says which model was passed, not which one runs. New draft author contracts describe harness, runner and platform duties, marking what's implemented and what's proposed.

#2239, #2243, #2272Link

rig expand keeps the member settings rig up accepts, including env, effort and startup settings, and a restore keeps a model set with rig seat set-model.

#2250, #2227, #2228Link

Viewer API: POST /api/terminal/viewer/ensure returns HTTP 400 for view_required and unknown_provider, where it returned 200 with an error body. Keep reading the body's code.

#2259Link

A verified exited process in a retained pane reads pane_exited, not running and idle, and its work goes to the usual recovery finding.

#2248Link