rigs

1# rigs: your route into OpenRig
2 
3OpenRig runs a team of coding agents (Claude Code, Codex and others) side by side in tmux. A local daemon keeps their
4tasks, messages and state, so the team keeps working across restarts. This skill gets OpenRig installed, gets a team
5working on what the person wants, and shows how to work with that team from here.
6 
7**The goal is a team doing the person's work, not just an install.** Go through the steps in order and stop early only
8if the person asks you to. When they say what they want built, give it to OpenRig's operator (step 2) instead of
9building it yourself.
10 
11Tell the person what you're about to run and why before you run it. Don't install system packages or change their
12machine without a yes, and don't start a team, including `rig up`, without their yes to what it will start; a yes they
13already gave for that same launch counts, so don't ask twice. Starting OpenRig and a team writes files: Codex hooks and settings in
14`~/.codex/config.toml`, Claude Code workspace trust in `~/.claude.json`, discovery skills in `~/.claude/skills` and
15`~/.agents/skills`, and, in the repository, managed guidance in `AGENTS.md` or `CLAUDE.md`, activity hooks in
16`.claude/settings.local.json` and a status line there unless the project already has its own, plus the team's skills
17and plugins. Unless a permission policy, a per-seat choice or (for Codex) a named profile applies, the kernel's own
18…