Skip to content

mvschwarz/openrig / packages/daemon/specs/agents/shared/skills/core/openrig-cmux

openrig-cmux

Verified

Use when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via `rig terminal --provider cmux`, or driving cmux on an agent's request. Same OpenRig view semantics as openrig-herdr (the verbs, honest-partial/degrade, read-only cross-rig, scroll/copy, same-size-only duplicates); cmux is the **best-effort** provider (herdr is the default and the proof-gated one). Prefer openrig-herdr unless cmux is specifically wanted.

openrig-cmux

cmux is a provider for OpenRig views — the same rig terminal surface as herdr, rendering the tiles into cmux instead. It is the provider OpenRig already shipped (the existing "Launch in cmux" affordance generalizes onto rig terminal <provider>), kept working. The OpenRig-semantic half is identical to openrig-herdr: OpenRig decides which agents form a view; the provider renders the pixels. Read openrig-herdr first for the full model — this skill only calls out what differs for cmux.

Provider status — cmux is best-effort

  • herdr is the default and the proof-gated provider; cmux is best-effort — it ships on the same rig terminal <provider> + web-launcher neighborhood, but a cmux miss is not a slice failure. Reach for cmux when it is specifically wanted; otherwise default to herdr (rig terminal open <view> with no --provider).
  • Views are provider-agnostic: the same view + the same agents + the same semantics carry across herdr and cmux. A saved view opens in either.

The surface (same three verbs, --provider cmux)

rig terminal open <view> --provider cmux [--json]   # open a view into cmux (herdr is the no-flag default)
rig terminal views [--json]                          # the same view library, provider-agnostic
rig terminal status --provider cmux [--json]         # cmux liveness / health

<view> resolves exactly as with herdr: a rig name · pod:<rig>/<podNamespace> · mission:<id> · slice:<id> (derived live) · a saved-view name.

What carries over unchanged from openrig-herdr

All of these behave identically — see openrig-herdr for the detail:

  • Honest-partial / honest-degrade — opened / absent / degraded, each named; partial opens exit 0, zero-pane exits non-zero; an http-registered host's agents degrade with the reason ("host <id> is http-registered; tiles need ssh"), never silently dropped.
  • Read-only policy — a rig or pod: view is interactive; mission: / slice: views are read-only by construction; a saved view is per-member (readOnly). A read-only pane is tmux attach -r (client readonly=1, keystrokes physically cannot reach the agent). See openrig-herdr.
  • Safety rails (the fleet-safety rail) — a tile is a view (nested tmux attach) of a daemon-owned session; never move/join/kill/re-parent a daemon-owned pane; closing a tile detaches one client and leaves the session untouched; never live-flip tmux options on a running seat in production (prove it in an isolated environment first).
  • Scroll + copy out of the box — the daemon's terminal defaults (per-session scroll at launch + the server's clipboard defaults); running seats pick up wheel-scroll at their next relaunch.
  • Limits — tile chrome v1 = a plain label; same-size panes for duplicate/multi-view membership (the different-size resize mismatch is an inherent tmux multi-client limit, documented not fixed).

cmux-specific notes

  • Open-or-focus per agent — cmux's shipped integration opens a node or focuses it if already open; expect focus (not a duplicate) when a seat is already tiled in cmux.
  • The shipped "Launch in cmux" affordance is preserved (byte-compatible) and generalizes into the provider + view picker; opening cmux from the web launcher still works.
  • No AGPL arm's-length concern — unlike herdr, cmux is OpenRig's shipped provider integration; the clean-room/never-embed rail that applies to herdr is not a cmux constraint. (This skill itself is still authored clean-room.)

Saved views — provider-agnostic

Saved views are hand-authored in terminal-views.yaml (v1 has no save/write verb) and are provider-agnostic — see openrig-herdr for the exact schema, the store facts (atomic tmp+rename, byte-stable, at the OpenRig home root), and the derived-views-never-persisted rule. Reopen any saved view in cmux with rig terminal open <id> --provider cmux. Derived views (a rig, pod:<rig>/<pod>, mission:<id>, slice:<id>) are computed live and never written to the file.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall