Published: @openrig/cli@0.6.1 is available on npm as latest.

:::sh
npm install -g @openrig/cli@0.6.1

OpenRig 0.6.1 — First-use repairs and one help path

OpenRig 0.6.1 improves first-use guidance, Codex readiness and linked-worktree launches, with a single help path and regression checks on pull requests.

Find help from the installed version

Ask your agent to read:

:::sh
rig context get help

The help guide brings together environment checks, setup and restart symptoms, permissions, instance layout and escalation. Its linked reference guides are included with the package too. If OpenRig cannot install or rig cannot run, use the guide online at openrig.dev/help/agents (www.openrig.dev), or read daemon/docs/reference/help.md inside the installed @openrig/cli package. For help, email hello@openrig.dev; a GitHub account is not required.

This is the canonical guide added in #113, with entry points from the README and agent startup guidance.

Read a catalogued project's execution view

:::sh
rig view show execution --project <catalog-id> --mission <mission> --json

The CLI now forwards the selected project and mission to the existing daemon resolver, which uses that project's configured missions root. Previously the CLI could only use the default workspace for this view. Omitting --project keeps the existing behavior. This does not add project inference from the current directory. Thanks to @dajiaohuang for #105.

Codex readiness and bundled guidance

• Startup/resume checks recognize Codex's » conversation prompt, including a fresh prompt after a dismissed hook-review panel. Numbered selection menus still require attention. Thanks to @dajiaohuang for #111.
• The bundled Vault skill has valid frontmatter, with a regression check for shipped skill headers (#115).
• Historical development evidence has been removed from the public source tree (#118). The retired spike/tui-drivability prototype was also removed (#119); the shipped TUI remains.

Identity readings and Codex launches

• Boot-time comparisons on non-UTC hosts: parse SQLite's zone-less boot timestamp as UTC. Identity and context-usage readers then compare observations with the actual generation start, avoiding time-zone shifts that could reject current observations or accept older ones. Thanks to @Coder8124 for #124.
• Custom Codex status lines: recognize an interactive conversation when its header has scrolled away and the status line puts a mixed-case model name after other fields. Unresolved trust, hook, update and model-selection gates remain in place. This is recognition only; the separate stale restore-warning behavior from #116 is not repaired here. Thanks to @Hexgunner69 for the report and @Aummadour for screen-derived regression cases included in #125.
• Linked Git worktrees: Codex fresh launches resolve the worktree's Git directory and common Git directory instead of treating its .git file as a directory. Resume/fork arguments and permission modes are unchanged. Thanks to @mgall-ibizdigital for the report, reproduction and suggested approach in #121, addressed by #126.

Regression checks on pull requests

#117 adds eight test jobs: build and package-file inspection, type checking, repository checks, four separate daemon/CLI/TUI/UI suites, and an installed queue-durability scenario. The latter checks a normal run, an intentionally introduced lost-baton failure and a healthy return. A checker that misses that seeded failure cannot pass.

The workflow uses Node 22, Linux runners for the build/repository/installed scenario jobs, and macOS runners for the four package suites. It does not run all eleven historical scenario seeds or certify every platform, provider or authenticated native-agent workflow.

Upgrade and compatibility

Node.js 22 and 24 remain the supported versions; Node 20 is unsupported. No dependency, engine, permission-mode or database-migration change is introduced by this maintenance release. Follow the existing upgrade procedure when updating an existing instance.

Package identities and the checks performed on each published artifact belong with its GitHub release. These source notes do not certify every platform or authenticated native workflow. Native permission enforcement across fresh launch, resume and fork retains the verification limits recorded for 0.6.0.

Slack app manifest/setup assistance and Rig Stream classification remain experimental. This release makes no new real-app, provider-run, accuracy or reliability claim for them. The existing Slack connector is not experimental. See the 0.6.0 limitations for retained boundaries.

Checks on this artifact

The exact package was installed in a disposable macOS 15.7.3 ARM64 guest with Node 24.21.0/npm 11.19.0. Consumer postinstall ran, SQLite 13.0.3 loaded its bundled prebuild, and database integrity and all 89 migration identities were checked. Two real Codex project agents completed a CSV-import repair and independently reviewed it; the final task check passed three regression tests.

This was an assisted custom-prefix installation: native login shells did not inherit that prefix. The initial agents located the absolute command, the operator corrected the TUI shell PATH, and a later fresh-agent orientation stopped at rig not found. Agent shells used Node 22; the daemon and final operator check used Node 24. This does not establish a completely unassisted installation on every platform.

Fresh launch and resume produced bounded observations. A native fork child was observed, but managed fork completion was not verified after a command timeout; do not interpret this as universal native permission-enforcement coverage. Pi was not tested and Herdr was unavailable in this run.

OpenRig remains intended for trusted local/private environments. This release does not claim hardened public-network deployment or add a manual UI-token setup requirement.

Artifact identity

• Source: d83bbebe97430c3f2777226fecc089d31e276aa8
• Tree: ed73fe548f6421374cae96aba7963d5683b45405
• Package SHA256: bf9aa3a78c2bf6ac887920485da7793545dd6a283d21120dd766b20da7454e87