# Gc Rigs

> Managing rigs — add, list, status, suspend, resume

- Skill: `gastownhall/gc-rigs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gastownhall/gc-rigs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gastownhall/gc-rigs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: gastownhall (https://skillmd.com/u/gastownhall)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gastownhall/gc-rigs

---


# Rig Management

A rig is a project directory registered with the city. Agents can be
scoped to rigs via the `dir` field.

## Beads

Each rig has its own `.beads/` database with a unique prefix (e.g.
`hw-` for hello-world). To create or query beads for a rig, route through
Gas City with the rig's configured name:

```
gc bd create "title" --rig <rig-name>   # Create in rig's database
gc bd list --rig <rig-name>             # List rig's beads
```

Running `gc bd` from the city root without `--rig` targets the city-level
store only when no stronger scope signal applies. Gas City also auto-detects
scope from a bead ID prefix, `GC_RIG`, or an enclosing rig/worktree. Use
`gc bd --city <city-path> ...` when HQ is required and `gc bd --rig
<rig-name> ...` when a rig is required. Use `gc rig list` to find configured
rig names and paths.

## Convention

The canonical location for rigs is `<city-root>/rigs/<rig-name>`. Always
use this path unless the user explicitly provides an alternative. Do not
create rigs at the city root or as siblings of the city directory.

If the user asks to create a rig but does not specify where, **ask them**
before proceeding: confirm the `rigs/` convention and offer the choice of
a custom path. Do not silently pick a location.

## Adding and listing

```
gc rig add <path>                      # Register a directory as a rig
gc rig list                            # List all registered rigs
```

## Status and inspection

```
gc rig status <name>                   # Show rig status, agents, health
gc status                              # City-wide overview (includes rigs)
```

## Suspending and resuming

```
gc rig suspend <name>                  # Suspend rig (all its agents stop)
gc rig resume <name>                   # Resume a suspended rig
```

## Restarting

```
gc rig restart <name>                  # Restart all agents in a rig
gc restart                             # Restart entire city
```