Understand workspace activity
Read delivery and activity charts with the right time range and attribution.
The Governance settings bring together model usage, velocity, and weekly session and task activity. Use these views to ask specific questions about how the workspace works, then follow the underlying records for detail.
Choose the right view
| View | Useful question |
|---|---|
| Model usage | Which models and teammates initiated turns? |
| Velocity | What delivery evidence is attributed to work in this workspace? |
| Sessions per week | How has session activity changed over time? |
| Tasks per week | How has tracked task activity changed over time? |
Select the offered time range, teammate filter, and grouping before comparing values. Model usage trends are shown per day in UTC. A session can have several teammate/model rows when different turns used different choices.
Read attribution with care
Human-originated sessions and integration-triggered automation are different sources. The identity that authorized an integration is not automatically the person who performed all work it triggers.
PR creation and merge are separate events. A chart organized by PR creation cohort can show later merges against the cohort that created the work. Do not assume every chart is grouped by the merge date.
Use the view's labels and linked records to understand its definition. A task count, turn count, merged PR count, and runtime total measure different things.
Use the records to investigate
Open the session, task, or PR behind an unexpected result. Check its origin, dates, model, and delivery evidence before changing team policy. A high activity count alone is not proof of useful delivery or unnecessary spend.
For funding and charges, inspect usage and limits and plans and credits. Activity charts are not a replacement for the current billing view.