Skip to main content
Users shows activity per developer — what they ran, what it cost, and how their agent runs went.
Users needs Analytics · View.

What’s on the page

Headline figures

Four cards across the top, covering everyone the current filters match rather than the page on screen.

Table

Headed Users with the total count. Twenty developers to a page. An info icon on each of the three run-quality headers explains what the number measures, and a column picker chooses which of Total Cost, Total Tokens, Tasks and Models are shown.

Filters and controls

Time range

The standard Analytics range selector applies.

Filters

Search users by name or email… narrows the table.

What you can do

A developer’s page

Total Cost, Total Tokens, Total Tasks and Avg Cost/Task for the range, a Model Usage by Cost breakdown showing what share of their spend each model took, and their tasks - with the work type editable on your own tasks, and never at Analytics · View. Their tasks are listed with: A Recent chip, a day picked on the heatmap and the Policy Enforcement filter all narrow the list; Clear date filter drops the day. A Token Breakdown splits their tokens into Input, Output and Cache. Where personal-account visibility is on for your organization, an Accounts card lists the vendor accounts they have signed in with: the tool, the account (or No sign-in detected where it was used without a sign-in that could be read, such as an API key or a gateway), a Personal badge for a personal account on a managed device, and the plan with a since date. Under Activity & Agentic Use sits the run-quality picture: weekly trends for clean-completion rate, median run and longest hands-off run, and an activity heatmap that always covers the last 12 months regardless of the range you picked, shaded Less to More with No activity on empty days. A developer with too little activity to score reads Insufficient signal, and a trend needing more weeks reads Not enough weekly data to draw a trend yet.
Longest hands-off run and Clean completion rate show how much your developers trust their agents. Both rising usually means the policies and setup are working.
Run-quality figures stay blank until a developer has enough agent runs in the window for the number to mean something: a developer with some runs but too few to score reads as a dash. A developer with no agent runs at all reads as zero, badged Light. To read either end of the distribution, sort Total Tokens — descending for your heaviest users, ascending for your lightest.

Messages you may see