Finding, creating, claiming, and closing work items (beads)
Routing work to agents with gc sling and formulas
API server and web dashboard — config, start, monitor
Managing agents — list, peek, nudge, suspend, drain
City lifecycle — status, start, stop, init
Sending and reading messages between agents
| name | gc-rigs |
| description | Managing rigs — add, list, status, suspend, resume |
A rig is a project directory registered with the city. Agents can be
scoped to rigs via the dir field.
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, run bd
from the rig directory or pass --dir:
bd create "title" --dir /path/to/rig # Create in rig's database
bd list --dir /path/to/rig # List rig's beads
Running bd from the city root hits the city-level .beads/, not
the rig's. Use gc rig list to find rig paths.
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.
gc rig add <path> # Register a directory as a rig
gc rig list # List all registered rigs
gc rig status <name> # Show rig status, agents, health
gc status # City-wide overview (includes rigs)
gc rig suspend <name> # Suspend rig (all its agents stop)
gc rig resume <name> # Resume a suspended rig
gc rig restart <name> # Restart all agents in a rig
gc restart # Restart entire city