Product / Developer Productivity
Understand AI adoption, spend and delivery.
Understand how your teams use AI coding tools, what providers report, and how repository work moves through review and merge. Read the signals together while preserving their separate meanings.
One engineering review. Distinct sources of evidence.
Developer Productivity brings connected coding-tool activity and code-host delivery patterns into their own reporting domain. Summary provides a starting point; the detailed reports explain the activity, spend and workflow behind it.
Summary
See adoption in context.
Review activity across configured Codex, Claude Code and Cursor sources alongside reported spend and repository delivery trends. The selected period, source health and mapping context make clear what the summary covers.
Developers & teams
Understand participation and contribution.
Review tool activity and repository contribution for the people and teams within your authorized scope. Mapping conflicts, unmapped activity and protected team coverage remain explicit.
These are signals for a responsible engineering discussion, not a performance ranking or score.
Delivery flow
See how work moves through review.
Review created and merged change requests, review-to-merge patterns, open backlog, backlog age and change-size coverage at repository level. Matched periods and data-through context support a consistent reading.
Delivery patterns describe the workflow; they do not prove that AI caused an outcome.
AI usage & model costs
Read what each provider actually reports.
Keep requests, sessions, active days and other native units separate. Review reported spend, estimated amounts and unavailable cost in their own categories, with model and source coverage attached.
Direct AI billing and cloud-hosted AI cost belong to cost management. A cost-catalog entry does not establish a Developer Productivity connection.
Manage connections
Keep access and mapping deliberate.
Owners and admins manage independently authorized coding-tool and repository connections. Source support, mapping review, entitlement and consent determine what can be reported.
Connections use narrow, content-free scope: no prompts, responses, source code, patches, comments, commit messages or filenames are collected. Activity retention is at most 90 rolling days.
A separate product for your engineering review.
Separately quoted and billed for Pro or Enterprise. Eligibility is confirmed during evaluation; owner/admin authorization and the add-on’s own entitlement apply.
Discuss Developer Productivity