Metrics

The Metrics page (/metrics) is where you watch the company's throughput and its spend. Four tabs: Performance, Token Usage, Delivery, and Scorecards (the active tab is in the URL as ?tab=).

Performance

The Performance tab is a snapshot of velocity and pipeline health, computed from the live task list and the orchestrator's agent status.

• Velocity — completed today, completed this rolling 7 days, total completed all-time, and a completion rate across all tasks.
• Task Status — a compact 2×3 grid of status tiles (Pending, In Progress, Blocked, Awaiting QA, Completed — each an icon, a label, and a count) paired with a donut chart of the same distribution. The grid gives you exact counts; the donut gives you the proportional shape, so you can read the pipeline health at a glance and cross-reference the numbers when you need them.
• Agent Status — how many agents are running, idle, waiting (need input), or in error.
• Team Health — one card per cell with a health score and its active / blocked / done breakdown. The score is a simple read on blockers: more blocked tasks pulls a cell's health down. A healthy cell sits near 100%; blockers visibly degrade it, so a cell sliding toward red is the signal to look at its blockers.

Token Usage

The Token Usage tab is the cost dashboard. A time-window selector — 24h / 7d / 30d / 90d — sits above everything and drives every card, chart, and table on the tab at once; it defaults to 24h. The 90-day option is the widest historical view and is useful for spotting monthly spend patterns and model-mix shifts.

• Summary cards — tokens in, tokens out, total tokens, total cost for the selected window, the trend versus the prior period, and dollars saved by prompt caching.
• Time series + model donut — usage over time, and the split across models.
• Per-agent and per-team bars — who and which cell is spending. Every chart on this tab has a Chart / Table toggle so you can switch from the visual to a sortable table of the same numbers.
• Monthly projection — projected monthly cost from a rolling-average daily run rate.
• Cache efficiency — cache hit rate and the cost it saved.
• Sessions table — the recent agent spawn sessions behind the numbers.

A window with nothing in it shows an explicit "no usage recorded" message in place of a chart, rather than an empty grid that looks like something failed to load.

Where the dollar figures come from

Cost is derived from per-session token counts using provider-aware pricing — and local / Ollama usage is intentionally priced at $0, so a self-hosted or Ollama-routed workforce shows tokens but no dollars. The full cost model, the budget cap, and where each number originates are documented in Cost & usage; this page only shows the numbers.

Delivery

The Delivery tab is the flow dashboard — not what the company shipped or what it cost, but how the work moved. Every panel is reconstructed from the task lifecycle history RoboCo already records (each status transition is logged), so it needs no extra bookkeeping. Cycle-time, bottlenecks, and rework look back 30 days; the scorecards look back 7.

• Cycle Time by Stage — the average time a task sits in each lifecycle stage (claimed, in progress, awaiting QA, awaiting documentation, awaiting PR review, awaiting PM review, …). This is where you see where the time actually goes — a tall "awaiting QA" bar means work waits on review, not on coding.
• Bottlenecks — the same data ranked by total time absorbed, with the single worst stage called out and a live count of how many tasks are parked in each stage right now, plus the current active-blocker count. It answers "what is holding the company up today?"
• Rework — how often work bounces back to needs_revision (the headline rate = reworked ÷ completed), broken down by cell and by agent, plus the token cost of that rework. Crucially, a bounce is attributed to the QA or PR-reviewer who sent it back, not the developer who owns the task — so a high QA fails number against a reviewer is a signal about that reviewer's gate, and a high rate against a developer is a signal about their first-pass quality.
• Cell scorecards — one card per cell (Backend / Frontend / UX-UI) with its completed count, average cycle time, rework rate, and cost over the last 7 days — the quick read on which cell is moving cleanly.

Scorecards

The Scorecards tab is the per-agent and per-org performance rollup, looking back a rolling 30 days — longer than the Delivery tab's 7-day cell scorecards, and a different cut from Delivery's stage-by-stage flow view: this one is about who (and the company as a whole) is producing.

• Organization — member count, tasks completed, first-pass yield (the share of completed tasks that shipped with no QA / PR-gate / PM / CEO bounce at all), throughput per hour of active agent runtime, total active effort hours, and cost.
• CEO (you) — your own numbers: approval count and its p50/p90 latency (how long a task sits in your queue before you act), unblock count and its p50 latency, and a count of your god-mode actions.
• Members — one row per agent (excluding you and the system account) with tasks done, first-pass yield, active effort hours, average turns per completed task, QA pass rate, escalations, how many times this agent's work blocked someone else, and utilization (share of spawned time actually spent working, not idle). A row still mid-task shows a live badge, since its numbers include in-flight work.

This is the same org-wide rollup summarized on the Command Center's quick-metrics row, with a deep link into the full tab from there.

Next

→ Cost & usage for the pricing model and budget cap · Health & metrics for operational monitoring · Command Center for the at-a-glance view.

llms.txt