TempoMeasure adoption from shipped work
Editor telemetry can tell you that an assistant was opened. Tempo connects AI usage to commits and pull requests, so adoption is measured where work enters the delivery system.
The dashboard tracks AI-assisted commits, AI-assisted pull requests, tool distribution, model metadata when available, and adoption trends over time. Results can be viewed across the organization, by repository, and by contributor.
- AI commit rate: detected AI-assisted non-merge commits divided by non-merge commits.
- AI PR rate: merged pull requests with at least one AI signal divided by merged pull requests.
- Tool breakdown: which supported coding assistants contributed to detected work.
- Confidence and method: whether attribution came from local CLI evidence or git forensics.
Compare adoption with delivery outcomes
More AI activity is not automatically better delivery. Tempo separates AI-assisted and manual pull requests so engineering leaders can compare the medians that matter.
Use the comparison to investigate whether AI-assisted work is moving faster, arriving in larger pull requests, or bypassing review more often. The result is a starting point for a team conversation, not an individual performance score.
- PR cycle time for AI-assisted versus manual pull requests.
- Median PR size based on additions and deletions.
- No-review rate for both groups.
- Changes in adoption and delivery across selected time windows.
Use local attribution when precision matters
Tempo CLI runs as local git hooks and can match committed files with local AI session data. It produces structured attribution metadata before an optional sync to Tempo cloud.
When CLI evidence is unavailable, Tempo can still identify explicit commit trailers and pull-request patterns. Every detection keeps its method and confidence so teams can distinguish strong evidence from weaker signals.
Tempo never treats a missing signal as proof that a commit was written without AI. Detection coverage depends on the evidence available.
Questions Tempo helps engineering leaders answer
The useful question is not “How much code did AI write?” It is “Where is AI changing the delivery system, and what should we do differently?”
- Which tools are actually present in shipped work?
- Is AI-assisted work waiting longer for review?
- Are AI-assisted pull requests larger or less frequently reviewed?
- Which repositories have adopted AI without degrading flow?
- Where should enablement, guardrails, or review capacity change?
Measure AI coding across four layers
A useful AI measurement program separates adoption from impact. Adoption describes where assistants are present; flow, quality, and cost describe what changed after that work entered the delivery system.
Read the layers together. A higher AI commit rate with shorter coding time can still create a review bottleneck if pull requests become larger or arrive faster than reviewers can absorb them.
| Layer | Signals | Decision it supports |
|---|---|---|
| Adoption | AI commit rate, AI PR rate, active tools | Where enablement or license coverage is changing |
| Flow | Cycle time, pickup time, review time, throughput | Whether AI-assisted work moves through delivery faster |
| Quality constraints | PR size, no-review rate, rework and failure signals | Where guardrails or review capacity need attention |
| Cost and coverage | Tool mix, attribution coverage, spend when available | Whether the evidence is complete enough to support an investment decision |
Turn the dashboard into a learning loop
Start with a baseline before a rollout or policy change. Review adoption weekly while behavior is changing, then compare delivery outcomes over a longer window that contains enough completed pull requests to reduce noise.
Use repository or team comparisons to generate hypotheses, not verdicts. Investigate the pull requests behind a change, agree on one intervention, and watch both the intended metric and its balancing signals.
- Baseline adoption, cycle time, PR size, and review behavior before the change.
- Segment by repository or work type before comparing outcomes.
- Choose one intervention, such as smaller batches or explicit review ownership.
- Revisit the trend and document what the team learned.
Frequently asked questions
What is AI coding analytics?
AI coding analytics connects evidence of assistant use to engineering artifacts such as commits and pull requests, then compares that work with delivery outcomes including cycle time, review load, size, and deployment flow.
Does more AI-generated code mean higher productivity?
No. Adoption is an input signal. Productivity requires context from delivery speed, quality constraints, developer experience, cost, and the outcomes the team is trying to create.
Can Tempo identify work from multiple AI coding tools?
Tempo records supported evidence from Claude Code, GitHub Copilot, Cursor, Windsurf, and Codex. Coverage depends on the local session formats and explicit metadata available for each tool.
Does Tempo upload prompts or source code?
No. Local attribution matches session evidence with changed files on the developer machine. The resulting metadata can be synced without uploading prompts, conversation transcripts, diffs, or source-code contents.
Sources and further reading
- DORA: Impact of generative AI in software developmentResearch on how AI adoption interacts with software delivery performance and organizational systems.
- SPACE framework for developer productivityThe original multidimensional framework for reasoning about developer productivity.
- Tempo AI coding detection methodologyThe evidence, confidence, privacy, and aggregation rules behind Tempo attribution.