mvschwarz/openrig
1
0 Fork 0
mirror of https://github.com/mvschwarz/openrig.git synced 2026-11-09 11:51:37 -10:00
Code Issues Packages Projects Releases 1 Wiki Activity

Release 0.3.3

Browse Source 
OpenRig v0.3.3 — final release (promoted from 0.3.3-rc.0
after vm-e2e fresh-install verify GREEN).

Promotes 0.3.3-rc.0 to @latest with one doc-fix correction
caught by the rc-verify proof bar:

- slice 17 ("send_text inline dash sentinel") was
  incorrectly described in the rc.0 release notes +
  openrig-user skill mirror as adding `rig send --body-file`
  to the CLI surface. That flag actually lives on
  `rig queue create` (shipped in v0.3.2 slice 21 FR-4).
  Slice 17 is a daemon-side adapter fix in
  packages/daemon/src/adapters/tmux.ts: the internal
  send_text path now carries an explicit `--` end-of-options
  sentinel so tmux no longer parses content starting with
  `-` or `--` as flag arguments. The `rig send` CLI surface
  is unchanged.

VM-e2e proof of the rc.0 binary (against the
registry-recommended openrig-qa-claude-codex-auth-ready-clean-20260503-v1
baseline) confirmed: fresh-install clean, daemon healthy,
archive/unarchive round-trip working, rig down by-name with
auto-snapshot honest, ps --include-archived JSON fields
clean, whoami --json honest-error path, no baseline drift.

This commit lands only the doc correction + version bump
0.3.3-rc.0 → 0.3.3 across 4 package.json files +
package-lock + the mirror-skills sync of the openrig-user
SKILL.md doc fix.

See docs/releases/v0.3.3.md and CHANGELOG.md for the full
release narrative.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This commit is contained in:
mvschwarzandClaude Opus 4.7 committed 2026-06-11 12:00:45 -07:00
1 parent b66095c2b2
commit b5ae76b474
8 files changed
+36 -33
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/releases/v0.3.3.md
+11 -10
View File
@@ -294,21 +294,22 @@ Same-name active+archived pair resolves the ACTIVE rig (not
ambiguous). Archived-only name does not resolve by name (use the
id, or `rig unarchive` first).
### `rig send --body-file -` for Stdin
### Send Text Inline Dash Sentinel (slice 17)
Inline payload delivery from a file or stdin, replacing the prior
temp-file folklore:
The internal tmux `send_text` path now carries an explicit `--`
end-of-options sentinel before user-supplied content, so tmux no
longer parses content beginning with `-` or `--` as its own flag
arguments. Companion to the slice 16 large-payload transport fix:
```
rig send <session> --body-file <path> [--verify] [--json]
rig send <session> --body-file - [--verify] [--json] # stdin
rig send <session> "content with -- dashes or - hyphens"
```
`-` reads from stdin. Mutually exclusive with `--body <text>`.
Kills the backtick-shell-corruption class for multiline send
bodies. Companion to the slice 16 / slice 17 transport fixes so
the surface no longer caps at the OS argv limit and no longer
breaks on dash-prefixed content.
delivers literally without the agent having to escape or work
around dash-prefixed leading characters (notably `---` YAML
frontmatter in per-seat startup payloads). This is a daemon-side
adapter fix in `packages/daemon/src/adapters/tmux.ts`; the
`rig send` CLI surface itself is unchanged.
### `rig send --verify` Delivery Outcomes
package-lock.json
Generated
+5 -5
View File
@@ -1,12 +1,12 @@
{
"name": "openrig",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "openrig",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"license": "Apache-2.0",
"workspaces": [
"packages/daemon",
@@ -7419,7 +7419,7 @@
},
"packages/cli": {
"name": "@openrig/cli",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"hasInstallScript": true,
"license": "Apache-2.0",
"dependencies": {
@@ -7450,7 +7450,7 @@
},
"packages/daemon": {
"name": "@openrig/daemon",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"license": "Apache-2.0",
"dependencies": {
"@hono/node-server": "^1.13.0",
@@ -7474,7 +7474,7 @@
},
"packages/ui": {
"name": "@openrig/ui",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"license": "Apache-2.0",
"dependencies": {
"@fontsource-variable/jetbrains-mono": "^5.2.8",
package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "openrig",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"private": true,
"license": "Apache-2.0",
"type": "module",
packages/cli/package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@openrig/cli",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"type": "module",
"description": "Local control plane for multi-agent coding topologies",
"keywords": [
packages/daemon/package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@openrig/daemon",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"private": true,
"license": "Apache-2.0",
"type": "module",
packages/daemon/specs/agents/shared/skills/core/openrig-user/SKILL.md
+8 -7
View File
@@ -434,17 +434,18 @@ rig send <session> "message"
rig send <session> "message" --verify
rig send <session> "message" --force
rig send <session> "message" --json
rig send <session> --body-file <path> [--verify]
rig send <session> --body-file - [--verify]
```
Use `--verify` when you want delivery evidence. Use `--force` only when you intentionally want to bypass activity-risk checks.
`--body-file <path>` reads the message body from a file; `--body-file -` reads
from stdin. Use either form to kill the backtick-shell-corruption class for
substantive bodies (the inline positional `"message"` form is fine for short
plain text). `--body-file` is mutually exclusive with the positional body
argument.
As of v0.3.3 (slice 17), content beginning with `--` or `-` is safe:
`rig send <session> "content starting with -- or - is now safe"` delivers
literally. The daemon's `send_text` path carries an explicit `--`
end-of-options sentinel so tmux no longer parses dash-prefixed content
as its own flags. The CLI surface itself is unchanged. For multi-line
or large bodies handed off as durable work, use
`rig queue create --body-file <path>` (`-` for stdin) — that's the
queue-side surface, not `rig send`.
`--verify` delivery outcomes (v0.3.3+):
- `delivered` — text + Enter both succeeded and capture re-confirmed the body landed.
packages/ui/package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@openrig/ui",
"version": "0.3.3-rc.0",
"version": "0.3.3",
"private": true,
"license": "Apache-2.0",
"type": "module",
skills/_canonical/core/openrig-user/SKILL.md
+8 -7
View File
@@ -434,17 +434,18 @@ rig send <session> "message"
rig send <session> "message" --verify
rig send <session> "message" --force
rig send <session> "message" --json
rig send <session> --body-file <path> [--verify]
rig send <session> --body-file - [--verify]
```
Use `--verify` when you want delivery evidence. Use `--force` only when you intentionally want to bypass activity-risk checks.
`--body-file <path>` reads the message body from a file; `--body-file -` reads
from stdin. Use either form to kill the backtick-shell-corruption class for
substantive bodies (the inline positional `"message"` form is fine for short
plain text). `--body-file` is mutually exclusive with the positional body
argument.
As of v0.3.3 (slice 17), content beginning with `--` or `-` is safe:
`rig send <session> "content starting with -- or - is now safe"` delivers
literally. The daemon's `send_text` path carries an explicit `--`
end-of-options sentinel so tmux no longer parses dash-prefixed content
as its own flags. The CLI surface itself is unchanged. For multi-line
or large bodies handed off as durable work, use
`rig queue create --body-file <path>` (`-` for stdin) — that's the
queue-side surface, not `rig send`.
`--verify` delivery outcomes (v0.3.3+):
- `delivered` — text + Enter both succeeded and capture re-confirmed the body landed.