Lifetime
Four headline totals for the whole life of your organization: workspaces created, compute minutes, PRs opened, and merge rate. Nothing here responds to the time controls, so it stays a fixed reference point.Trends over time
Organization-wide charts for the range picked in this section’s header. Usage runs full width on top, with Pull requests and Workspaces created side by side beneath it.Usage
A time series of compute minutes broken down by workspace source, so you can see how much agent runtime you’re consuming each period and where it comes from. Every minutes figure on the page carries its hour equivalent in brackets. Compute minutes are metered agent runtime (grants and bonus credits are excluded, so this tracks usage only); plan limits and charges live in Billing. Usage is populated from newly recorded debit events going forward; minutes billed before this tracking began are not backfilled and will not appear.Pull requests
A time series of pull requests created, merged, and closed so you can track how much agent work is landing. Merge and close rates use the PRs opened within the selected range as the cohort, so they reflect the outcome of that cohort and never exceed 100%.Workspaces created
A total for the selected range plus a horizontal bar breakdown of where those workspaces came from (dashboard, API, automations, Slack, Linear, GitHub, GitLab), ranked most to least, colored by source. Each bar shows its source count at the right edge.Inference activity
Agent runtime for the selected range, ranked by harness, model, and credential. Model rows keep the harness that ran them, while credential rows combine the harness, credential method, and scope (user or org), so admins can see whether personal or shared organization credentials account for the most agent time. Missing models and credential scopes remain visible as unknown, while missing credential methods appear as unattributed.
Inference activity records chat turns from the new activity pipeline going forward. Earlier turns are not backfilled, and its agent-time total is separate from metered compute minutes.
Below the runtime rankings, Skill calls and MCP calls show which skills and MCP servers were invoked most often in the selected range. These counts use the same forward-only activity pipeline and are not backfilled.
User drilldown
Per-person figures for the range picked in this section’s header, which is separate from the one on Trends over time so you can compare a person’s month against the organization’s year.Leaderboard
A per-person ranking for the selected range: each row shows the member’s rank, the member (avatar, name, and email), compute minutes, PRs opened, merge rate (share of the PRs they opened in-range that merged), and their top source (the workspace source they use most, colored to match the other cards). Members are ranked by compute minutes, highest first. Every member is listed, so people with no usage in the range appear at the bottom with0 minutes, 0 PRs, and N/A for merge rate and source.
Select any row to expand a breakdown for that member: the sources they create workspaces from, and their Activity heatmap. Both arrive with the row itself, so expanding one costs no extra request. PRs are credited to whoever opened them, so a member’s merge rate can never exceed the PRs they opened themselves.