Openrig Cmux logo

Openrig Cmux

CommunityPopular
mvschwarz
openrig-cmux

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.

Overview

Publishermvschwarz
Repositoryopenrig
Skill nameopenrig-cmux
Stars
5K
Forks
366
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mvschwarz on GitHub. Read the source before you install it.

Installation

Install the Openrig Cmux AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/core/openrig-cmux
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mvschwarz/openrig.git /tmp/openrig
mkdir -p .claude/skills
cp -r /tmp/openrig/packages/daemon/specs/agents/shared/skills/core/openrig-cmux .claude/skills/openrig-cmux
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Openrig Cmux in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Openrig Cmux on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Openrig Cmux is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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)

bash
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.

Frequently asked questions

What does the Openrig Cmux AI skill do?

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.

Why use Openrig Cmux on TypingMind?

Because you install it once and use it with any model. Openrig Cmux is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Openrig Cmux in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/core/openrig-cmux. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Openrig Cmux?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Openrig Cmux?

As many as you like. As long as a model supports skills, you can use Openrig Cmux with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Openrig Cmux AI skill free?

Yes. It is published on GitHub by mvschwarz under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇