ワンクリックで
ワンクリックで
Finding, creating, claiming, and closing work items (beads)
Routing work to agents with gc sling and formulas
Managing agents — list, peek, nudge, suspend, drain
City lifecycle — status, start, stop, init
Sending and reading messages between agents
Managing rigs — add, list, status, suspend, resume
| name | gc-dashboard |
| description | API server and web dashboard — config, start, monitor |
The dashboard is a web UI compiled into the gc binary for monitoring
convoys, agents, mail, rigs, sessions, and events in real time.
The dashboard is a separate web server. It needs a GC API server to talk to, but it no longer has to be launched from inside a city directory.
If you are using gc start without the machine-wide supervisor, the dashboard
talks to that city's own API server. Ensure the city API is enabled in
city.toml:
[api]
port = 9443
Then start the city normally with gc start. The API server starts with the
controller on that port.
If you are using the machine-wide supervisor, the dashboard talks to the supervisor API instead. The default supervisor API address is:
http://127.0.0.1:8372
In this mode, per-city [api] ports are ignored. The dashboard detects
supervisor mode automatically via /v0/cities, enables a city selector, and
routes requests through /v0/city/{name}/....
gc dashboard # Supervisor-only view from anywhere
gc dashboard --port 3000 # Same, custom dashboard port
gc dashboard serve # Explicit subcommand; same discovery
gc dashboard --city /path/to/city # Optional city context for standalone discovery
gc dashboard --api http://127.0.0.1:8372 # Optional override
gc dashboard auto-discovers the right API server in this order:
[api] listener.The --api flag remains available as an override for non-standard setups.
The dashboard provides:
Real-time updates via SSE (Server-Sent Events) from the API server.