API server and web dashboard — config, start, monitor
59
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./internal/bootstrap/packs/core/skills/gc-dashboard/SKILL.mdThe 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 = 9443Then 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:8372In 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 overridegc 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.
f530008
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.