OpenRig v0.5.15 — first-use recovery, software factory guidance and Pi fixes

Changes for version 0.5.15. Publication status and date are recorded on the GitHub release and npm.

OpenRig 0.5.15 improves startup and recovery, adds public guidance for a continuing software team and user-chosen command permissions, and fixes Pi reply visibility, shell context and terminal input handling.

Start and return with clearer guidance

Before launching, read what OpenRig changes on your machine. Provider integration can configure executable hooks and workspace trust; changing only OPENRIG_HOME does not isolate provider configuration. The getting-started guide walks through your first task and explains these setup effects.

Check the commands available in your installation:

:::sh
rig --version
rig --help
rig up --help

Startup and recovery recognize native Codex through shell and Node launchers, and report uncertainty when process identity cannot be established. Recognized update notices are skipped without installing provider updates. Authentication and trust choices remain yours.

Startup errors now describe the problem and a recovery action. If a name matches both a starter and a stopped rig, rig up <name> --existing selects the existing rig. Inspect its reported state before assigning more work.

Continue useful reviewed work

Give your agent a real repository, an outcome and the decisions you want to keep. The bundled OpenRig Software Factory recipe supports direct team work, queue-supported orchestration or an optional explicit Workflow.

:::sh
rig context show skills/core/openrig-software-factory --json
rig context get skills/core/openrig-software-factory/SKILL.md
rig context get skills/core/openrig-software-factory/references/worked-example.md

Start with the two-seat team. Add one or two seats with rig grow when the work benefits from separate responsibilities. The example covers roles, context, work ownership, independent review, concurrency and cost, and distinguishes changes to the running team from saving an updated RigSpec. Use guidance matching your installed version.

Choose command permissions

Ask your agent to inspect the target harness, explain the available scopes and apply your choice while preserving existing rules:

:::sh
rig context get skills/applying-a-permission-policy/SKILL.md

Allowing the whole rig command family includes lifecycle and configuration changes as well as reads. Choose narrower commands or retain approval prompts when appropriate. Project-only setup requires supported, active and trusted project configuration; if it is unavailable, the agent should explain the limit instead of substituting user-wide permission. Back up touched files and verify the selected rules in the actual conversation. Shipped sandbox, approval and permission defaults are unchanged.

Known compatibility limitation

On macOS arm64 with Node 24, installing the SQLite dependency can fail when a suitable prebuilt binary is unavailable and compilation is not available. Compiler-built SQLite has also failed during database cleanup at runtime. Use Node 22 on macOS arm64 for now. This recommendation does not change the declared Node support range, and this version does not update SQLite.

Pi replies, input and recovery

Pi replies and tool progress are visible for the supported RPC event shapes. Shell tools retain the managed OpenRig context needed for identity and routing. Provider errors are shown with bounded text, and exhausted retries do not print the same error repeatedly.

Pasted messages wait for explicit submission. The terminal runner accepts input beyond the terminal's canonical buffer limit, preserves editing and cancellation, and recovers after rejecting an oversized framed message. This is not a general latency guarantee or an unrestricted input-size promise.

An added seat whose first startup failed during resource projection, before its startup context was saved, can use the guarded retry after the setup problem is corrected. Retain the complete original member fragment and its source root; a snapshot alone does not reconstruct missing startup configuration. Use one retry at a time. Ordinary conversation resume remains separate.

Pi support is qualified and supervised. Controlled coding, follow-up, reporting and conversation continuity were verified with Pi 0.87.1 and OpenRouter z-ai/glm-5.3-flash; ordinary-seat identity, tools and a reply also worked. Completion of an ordinary useful task and unattended team operation remain unverified. Context-profile selection and hook-generation coverage are limited; do not assume parity with every Codex or Claude integration. The Software Factory guide likewise does not establish fully unattended operation.

Contributors and included pull requests

Thanks to @danielkuykendall23-boop for the Pi reply fix in #37, and to @mvschwarz for Codex startup and restore guidance (#38), Software Factory and permission guidance (#39), contribution and support guidance (#45), and the first-use README (#46).

This release also includes the startup-identity refinements, guarded first-start retry, Pi shell/error handling and terminal-input fixes described above. Project work-policy features and the Node 22/SQLite 13 upgrade are outside this release.

---

npm publication status: verified. @openrig/cli@0.5.15 is available from npm; the registry tarball matches the verified release artifact.