Agents Command Center

The Command Center is the project's top-level agent surface, at /a/<account>/p/<project>/agents. It answers three fleet questions at a glance — how many agents ran anything, how many runs shipped, and how much you spent — and lets you scan every agent side by side. It's the account's landing page after sign-in.

KPI strip

Five fleet-scoped tiles sit at the top, all computed from the current project's agents:

Tile	What it shows
Agents	Total agents installed on the project
Active	Agents that ran in the last 15 minutes
Runs (24h)	Total runs in the last day, split succeeded vs errored
Avg success	24h succeeded ÷ total, with a green/amber/red chip
Cost (MTD)	Month-to-date spend, with today's cost as a hint

Roster table

Each agent is one row. Columns:

• Status dot — green (ran in the last 15 min), grey (idle), amber (last run failed), red (revoked or suspended).
• Agent — icon, display name (links to the agent detail page), and slug.
• Kind — Interactive or Proxy.
• Runs (24h), Success (a bar plus percentage), Trend (a 7-day sparkline, or a "No Data" chip), Cost (MTD), and Cap (spend-cap utilisation).

Every column except the status dot, kind, and trend is sortable — click a header to toggle ascending/descending.

Search, sort, and filter

The roster state lives in the URL, so any view is shareable with a teammate:

• ?search=slack — filter by display name or slug (case-insensitive).
• ?sort=cost:desc — sort key (name, runs, success, cost, cap) plus direction. Default is runs:desc.
• ?kind=interactive — narrow to interactive, proxy, or all.

For example, ?sort=cost:desc&kind=interactive&search=slack renders the same sorted, filtered view for anyone you send the link to.

Live updates

The roster refreshes itself. Runs starting and finishing move the status dots and bump the Runs, Cost, and Active values within about two seconds, over a live connection. If that connection drops, a 30-second auto-refresh takes over, so the roster is never more than 30 seconds stale.

Where to go next

• Running agents to dispatch an agent and read its run history.
• Create an agent to add one to the roster.