Analytics
Review knowledge, delivery times, tool usage, and estimated coding costs across your repositories.
Analytics shows recorded activity across your connected repositories. It has four tabs: Knowledge, Velocity, Usage, and Value. Organization admins can use the repository and date-range filters to choose what to review.
Knowledge
See how your knowledge base is growing: captured entries, repositories with a knowledge base, recent additions, and a breakdown by entry type. This includes learnings, conventions, and recipes.
Velocity
See how long issues spend in the workflow. Completed issues show time spent planning, awaiting implementation, and being implemented. Use this view to identify where work waits or takes longer.
Usage
Review daily skill activity, issue workflow activity, model usage, coding-agent usage, and CodeLantern tool calls. The coding-agent filter narrows session activity to a particular environment, also called a harness. It does not filter CodeLantern tool calls.
Session-based measurements can include tokens and estimated costs where the coding environment supplies them. CodeLantern tool activity shows calls and failures against connected providers. Reload the page to refresh the data; if a section fails to load, use its retry action.
Value
Review estimated cost by issue, then open an issue to inspect its contributing sessions, skills, and token usage.
Costs are estimates based on published model API rates. They do not represent your subscription bill, and actual provider charges may differ. A missing measurement is unknown, not zero; partial measurements do not describe the full cost of the work.
Missing or incomplete data
Session-based Usage and Value measurements require Value Telemetry and a coding environment configured to capture sessions. Tool-call activity and session measurements describe different activity and may have different coverage.
If a view is empty, check the repository and date filters, then confirm that relevant activity has been recorded. For missing sessions, check the organization's telemetry setting and developer setup. Enabling collection does not add earlier sessions. Some coding environments do not provide every measurement, so an unknown cost or token count does not mean nothing was used.