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
Sending and reading messages between agents
Managing rigs — add, list, status, suspend, resume
| name | gc-city |
| description | City lifecycle — status, start, stop, init |
A city is a directory containing city.toml and .gc/ runtime state.
gc init # Initialize city in current directory
gc init <path> # Initialize city at path
gc start # Start city under the supervisor
gc start <path> # Start city at path under the supervisor
gc supervisor run # Run the supervisor in the foreground
gc start --dry-run # Preview what would start
gc stop # Stop the current city
gc restart # Stop then start
gc init and gc start register the city with the machine supervisor,
ensure it is running, and trigger an immediate reconcile. Interactive
sessions are created separately with gc session new <template>.
gc status # City-wide overview
gc session list # Session / agent status
gc rig status <name> # Rig status
gc suspend # Suspend entire city
gc resume # Resume suspended city
gc config show # Show resolved configuration
gc config explain # Show config layering and provenance
gc doctor # Run health checks
gc events # Tail the event log
gc event emit <type> [data] # Emit a custom event
See gc skills dashboard for full dashboard reference.
Packs extend Gas City with additional commands, prompts, formulas, and
doctor checks. Pack commands appear as top-level gc <pack> <command>
subcommands.
gc pack list # List installed packs
gc pack fetch # Fetch remote packs