跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

rigs

Use when the user mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That includes installing, setting up, starting or updating OpenRig, seeing or getting back to their OpenRig agents, TUI or operator, starting or sharing a team, and joining this session to one.

mvschwarz · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mvschwarz/openrig --skill rigs

技能说明


name: rigs description: Use when the user mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That includes installing, setting up, starting or updating OpenRig, seeing or getting back to their OpenRig agents, TUI or operator, starting or sharing a team, and joining this session to one.

rigs: your route into OpenRig

OpenRig runs a team of coding agents (Claude Code, Codex and others) side by side in tmux. A local daemon keeps their tasks, messages and state, so the team keeps working across restarts. This skill gets OpenRig installed, gets a team working on what the person wants, and shows how to work with that team from here.

The goal is a team doing the person's work, not just an install. Go through the steps in order and stop early only if the person asks you to. When they say what they want built, give it to OpenRig's operator (step 2) instead of building it yourself.

Tell the person what you're about to run and why before you run it. Don't install system packages or change their machine without a yes. Starting OpenRig and a team writes files: Codex hooks and settings in ~/.codex/config.toml, a discovery skill in ~/.claude/skills and ~/.agents/skills, and, in the repository, managed guidance in AGENTS.md or CLAUDE.md plus the team's skills and plugins. Say so before you start OpenRig (the full list).

1. Install OpenRig, if it isn't installed

  • Check first: rig --version. If it prints a version, go to step 2.
  • What it needs: macOS or Linux, Node.js 22 or 24, tmux, and Claude Code or Codex signed in. Check only what's missing: node --version, tmux -V, claude auth status or codex login status.
  • Install: npm install -g @openrig/cli, then rig preflight (Node, tmux, the daemon port and state folders) and rig doctor.
  • Then go on to step 2: say it's installed and ask what they want worked on, and in which repository. A plain "install OpenRig" includes this. Stop here only if they say not to start a team.
  • If something fails: rig context get help is the help guide for the installed version. If rig itself won't run, use https://www.openrig.dev/help/agents. Getting started: https://openrig.dev/docs/getting-started

2. Open OpenRig and give its operator the goal

  • Start OpenRig: rig daemon status, and rig daemon start if it isn't running. rig preflight and rig doctor don't start it. Starting it also starts OpenRig's own team, the kernel, whose operator sets up the person's team. Keep it.

  • Show them OpenRig, the handoff: once OpenRig is running, open the OpenRig TUI and operator for the person. Say you're opening it, then run rig terminal open saved:kernel --window on the daemon's desktop. This is the next step after installing or starting OpenRig, and the way back whenever they want their agents or OpenRig again. Don't wait to be asked or for particular words. If they've said not now, give them that command for later. It opens a view itself, using herdr when installed or plain tmux otherwise:

    • Inside Herdr (you run in a Herdr pane): it switches the person's Herdr to an openrig kernel space, reusing a live one. No new window and no macOS prompt; their own spaces stay in the sidebar.
    • In Terminal or Ghostty: a new tab or window the size of theirs.
    • From Claude Desktop, iTerm or VS Code on a Mac: a new Ghostty window when supported, otherwise Terminal. Only here, tell the person before running it that Allow is fine if macOS asks to control that app. echo $TERM_PROGRAM $__CFBundleIdentifier tells you where you run. herdr, Apple_Terminal or ghostty, or tmux with com.apple.Terminal or com.mitchellh.ghostty, mean no macOS prompt, so don't mention one. tmux with anything else (iTerm, VS Code) can prompt, so say Allow is fine first.
    • Layout: under 120 columns the operator fills the first page; from 120, the dashboard and operator share it. The advisor has its own tab or tmux window.

    Then tell the person in a sentence or two where it opened and that the operator is ready for what they want to build. Don't list agents or statuses (the TUI shows them), and don't suggest a command for them to type. Preserve the current terminal. If OpenRig's notes say it couldn't confirm the view, say so plainly. If it's already open, point them to it rather than opening another. Only if the window cannot open, rig tui --shared is the dashboard-only fallback; explain the failure and help with the chosen fallback. Herdr is visible only in a terminal the person can see; switching the shared TUI to :terminals does not open one. No and headless/SSH use are valid background outcomes. Provider-only --provider herdr or --provider cmux is for an existing provider workspace, not the first desktop window.

  • If the window can't open, or over headless SSH: say plainly that no visible terminal was opened, and ask the person to open a new terminal window or tab on the daemon's host. Over SSH, that's a new SSH session to it with the known account. If you only know an HTTP daemon address, ask for the SSH details rather than inventing them. Then give them one complete command:

    • The command OpenRig printed: when rig terminal open saved:kernel --window can't open a window, it says why and ends with run: and a command (the error field with --json). That command already names the installed herdr binary and the daemon's socket, or the conversation to attach. Relay it exactly rather than composing one. If a note asks you to place the view once Herdr starts, run that rig terminal open yourself after they start it.
    • If it printed no command: find operator.agent in `rig ps --nodes --rig kernel --json --fields logicalId,canonicalSessionName,tmuxAtt
阅读完整来源 ↗