Project Statistics
- Desktop app
- All plans
What it does
A per-project panel showing activity, model spend and Cost per shipped ticket, with project, team and UTC date filters. Project activity comes first with the lifetime cards (Time open, Active, Idle, Avg active agents, Prompts, Agents opened, Tokens, Cost). Factory efficiency follows, comparing the selected period with the preceding period of equal length and showing the included tickets and runs. The By day chart and By agent table come last. Each section starts open and folds independently when you click its heading; filters and pagination are preserved until the panel closes.
Where to find it
- Right-click a project in the sidebar (or open its menu): Project statistics.
- The feature can be switched on or off in Settings > Features > Project statistics.
How to use it
- Run agents on the project as usual; time, prompts, tokens and cost are recorded in the background.
- Open Project statistics from the project's menu. Read the cards in Project activity first; click its heading to fold it.
- In Factory efficiency, choose the project, team and dates. Compare Cost per shipped ticket with the preceding period.
- Expand How costs are attributed, an included ticket, or the period's runs to inspect the calculation. Refresh sends pending costs before reloading; it is separate from the section's fold button.
- Read By day and By agent below for the existing lifetime activity breakdowns.
A project with no recorded activity shows No activity recorded yet.
Settings
featureFlags.projectStats(global, Settings > Features): show or hide the feature.
Agent tools (MCP)
None. The panel is a read-only view for the user.
Providers
All providers. Tokens and cost are summed across every agent of the project whatever CLI it runs; cost is indicative, derived from a static rate card, and does not reflect a flat monthly subscription.
Mobile
Not on the mobile companion.
Limits
- Factory cost records are saved to your account and merge observations from multiple computers. Local storage is an offline queue; costs sync every minute and before reading the report.
- Shipped means currently Done, excluding Won't fix, with a completion date in the selected UTC period. Reopening removes the ticket until its next completion date.
- Attributable cost includes all recorded runs linked to the shipped tickets, even outside the selected dates. Period spend includes unfinished and unassigned work; it has its own ratio per shipped ticket.
- Team attribution is recorded at execution time. A multi-team ticket counts once per selected team and once overall.
- Recording starts with this update; old activity totals cannot be assigned retrospectively. Missing prices and resumed sessions make the amount a lower bound, shown as ≥. Unknown costs and ratios with no shipments are unavailable, never silently zero.
- Cost is an estimate for guidance, not an invoice, and depends on the provider exposing token counts.
- No export; the panel is meant to be read on screen.
Common questions
- Do I have to start a timer? No. Active and idle time are derived from agent sessions automatically.
- Does the cost include every agent? The period total includes all observed project spend. Cost per shipped ticket only includes runs linked to the included tickets; unassigned spend is shown separately.
- Where does the data come from? Your desktop records agent usage and sends it to your account. The server combines cost observations and backlog completion dates; the report does not depend on optional telemetry sharing.
- I cannot find the entry. Check Settings > Features > Project statistics is on.
Related
- Claude Code Token Usage: live token and quota tracking per agent.
- Agent Status Tracking: the statuses the active / idle split is built from.