Product boundary
Developer Productivity is separate from cost-source authentication and from the AI cost analyst. Buying Pro or Enterprise does not by itself grant access. The workspace must have the separate entitlement, and the current user must be an Owner or Admin.
AI coding-tool sources
- OpenAI Codex reports activity from an approved ChatGPT or OpenAI organization source.
- Anthropic Claude Code reports activity from an approved Claude or Anthropic organization source.
- Cursor uses its own productivity connection.
- GitHub Copilot Business or Enterprise is an AI-usage source, not a GitHub repository connection.
Provider metrics retain their native definitions and units. Missing cost, activity, model, or attribution fields remain unavailable. PruneFox does not rebuild reported cost from list prices.
Repository context
GitHub.com, GitLab.com, Bitbucket Cloud, GitHub Enterprise Server, and GitLab Self-Managed can provide separately authorized read-only change-request metadata. They are code hosts, not AI tools or cost providers.
PruneFox does not collect source code, diffs, patches, pull-request bodies, comments, commit messages, branches, or filenames. Repository evidence remains bounded to the scalar metadata needed for the reporting views.
Reporting views
Summary
Review the reporting period, data-through boundary, configured source outcomes, and the available team-level signals before interpreting a metric.
Developers & teams
Compare activity only within the selected scope. Named detail requires the additional responsible-use acknowledgement. Default order is alphabetical; ranking, performance labels, and cost or activity sorting are not provided.
Delivery flow
Review repository-level change, review, merge, and backlog patterns from scheduled snapshots. These signals do not prove that an AI tool caused a delivery outcome.
AI usage & model costs
Read provider activity in its native unit and keep reported, estimated, and consumption-only cost evidence separate. Gaps and unavailable model coverage remain visible.
Attribution and responsible use
Provider activity and delivery evidence are correlated reporting signals. They are not employee scores, causal productivity measures, or recommendations for hiring, compensation, promotion, discipline, or termination.
Exact change-request attribution is shown only when the source supplies trusted exact evidence. Period totals are never divided across individual pull requests. Small cohorts are suppressed, and named individual detail requires the current responsible-use acknowledgement.
Retention and access
Activity and normalized facts are retained for at most 90 rolling UTC days. Raw replay data is retained for at most seven days. Configuration and approved mappings may remain while the connection exists.
Manage connections
Connection management is a separate signed-in destination. Select the provider and plan or source first, then follow only the fields and authentication method returned for that workspace. A source can be described here without having a working self-service setup path.