OpenRig v0.5.16 — choose the Claude instruction file

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

OpenRig 0.5.16 lets a rig keep its managed Claude Code instructions out of a tracked CLAUDE.md, and adds an advisory portability report for pull requests.

Keep a tracked CLAUDE.md unchanged

OpenRig writes its instructions for Claude Code members into managed blocks in each member's working directory. By default that file is CLAUDE.md. If your repository tracks CLAUDE.md, select CLAUDE.local.md in the rig spec:

:::yaml
managed_blocks:
  claude-code: CLAUDE.local.md

Claude Code loads CLAUDE.local.md from the working directory as well; keep it out of git, for example with a .gitignore entry. The selection applies when members launch, restore, relaunch or are added, and it is kept by rig export and rig bundles. rig down removes OpenRig's blocks only from the selected file. OpenRig never edits, moves or deletes blocks in the other file.

Only the claude-code key is accepted, with CLAUDE.md or CLAUDE.local.md; any other key or value is rejected before a member launches. Without the field, behavior is unchanged. Codex members always use AGENTS.md.

Switching an existing rig: blocks OpenRig already wrote into CLAUDE.md stay there. Until you remove them, the file stays modified and Claude Code loads both copies. Delete each <!-- BEGIN OpenRig MANAGED BLOCK: … --> … <!-- END OpenRig MANAGED BLOCK: … --> section by hand and keep the rest of the file. If CLAUDE.md has no other uncommitted edits you need to keep, you can instead run git restore CLAUDE.md; that command discards every unstaged change to the file, not only OpenRig's blocks. See the RigSpec reference.

Portability report for pull requests

A new pull-request workflow lists added lines that contain values tied to one machine, network or account: credentials, home and temporary paths, network addresses and email addresses. Suspected credentials are withheld from the report. Findings never fail the check; the author decides what to change. It is pattern-based and does not guarantee that nothing private remains. Run it locally with:

:::sh
node scripts/portability-report.mjs

Contributors and included pull requests

Thanks to @hvpaiva for reporting and proposing the Claude instruction-file option in #25, and to @mvschwarz for the README badges and demo (#54) and the portability report (#56).

The Node support range and SQLite version are unchanged. The macOS arm64 with Node 24 SQLite installation limitation noted for 0.5.15 still applies; use Node 22 on macOS arm64.

npm publication: verified available as @openrig/cli@0.5.16.