Install the CLI
One npm install. Then verify it works.
npm install -g @rigxyz/cliThat's it. The rig command is now on your PATH.
rig --versionIf you're using Claude Code, the installer also drops a small skill at
~/.claude/skills/rig/SKILL.md so Claude knows what rig is and what to do
when you say "start a rig here" or "publish this". See
The rig skill for details.
To opt out of that skill install:
RIG_SKIP_SKILL_INSTALL=1 npm install -g @rigxyz/cliWhat got installed
| What | Where |
|---|---|
rig CLI | $(npm prefix -g)/bin/rig |
| Auth + config | ~/.config/rig/config.json (created on first rig login) |
| User-level Claude skill | ~/.claude/skills/rig/SKILL.md (skipped if ~/.claude/ doesn't exist) |
For collaboration only
If you'll be working on a shared rig, you also need the sync daemon:
npm install -g @rigxyz/tapdtapd is the local process that watches your files and ferries changes
through the relay. You'll never invoke it directly — the rig workspace
verbs (rig share, rig status, rig resume) shell out to it for you. It's
a separate package so non-collaborators don't pay for it.
Upgrade
npm install -g @rigxyz/cli@latestUninstall
npm uninstall -g @rigxyz/cli
# and if you installed it:
npm uninstall -g @rigxyz/tapdThe user-level skill at ~/.claude/skills/rig/SKILL.md is not removed
automatically; delete that file manually if you want it gone.
Next
- Quickstart: install a rig — try it on a real rig.
- Quickstart: create a rig — package your own workspace.