Cursor: Expanded Metrics Guide
Cursor provides detailed insights into AI usage patterns via the Admin Panel export CSV and Admin API. These metrics allow admins to track code origin, suggestion interactions, and chat-based adoption for each developer on a daily basis.
🔍 Metric Categories
Area
Metrics Covered
AI Contribution
AI vs Manual LoC, Accepted Lines Added, Composer Suggestions
Interaction Metrics
Tabs shown, Tabs accepted, Chat completions, Suggestions applied
Coverage & Activity
Active status per user per day, Usage trends over time
Engagement Intensity
Files edited, Commit activity, Frequency of usage
🧮 Key Metric Definitions
✅ AI Lines vs Manual Lines
AI Lines = Accepted Lines Added + Accepted Lines Deleted
Manual Lines = Lines Added + Lines Deleted (excluding AI lines)
Note: Only lines inserted via accepted AI suggestions are counted as AI lines.
✅ Suggestions Shown / Accepted
totalTabsShown: The total number of suggestions displayed to the developer (autocomplete or inline suggestions).
totalTabsAccepted: The total number of suggestions accepted by the developer into the code.
totalAccepts: Includes all types of accepted completions, such as Composer or Chat suggestions.
totalApplies: Represents the final, user-confirmed inserts into the code editor.
✅ Acceptance Rate
Formula:
Updated Explanation: The Acceptance Rate is a percentage of displayed suggestions that were accepted.
👤 User Classification
✅ Active Users
A user is marked as active if they:
Received a suggestion.
Edited a file with Cursor open.
Opened Cursor Composer (chat).
Accepted a suggestion.
❌ Inactive Users
A user is marked as inactive if no AI interaction occurred on a given day, even if the IDE was open.
Coverage: Coverage charts reflect the percentage of active users daily or weekly.
Hivel Calculations for Active/Inactive Users:
Active Users = Number of unique users with isActive = true at least once in the selected period.
Inactive Users = Total unique users (with any usage record) - Active Users.
🧱 Technical Foundations
Tracking: Metrics are tracked on a per-user, per-day basis.
Reset: Metrics are reset daily, with historical data available for up to 90 days prior to your integration.
⚠️ Known Limitations
Copy-pasting: Copy-pasting content from a suggestion without accepting it via the IDE does not get counted.
Modified Usage: Rewrites or edits inspired by suggestions are not tracked.
Offline Use: No data is captured when Cursor is used offline.
Summary: Cursor's metrics primarily track explicit interactions with AI suggestions and not actions like copy-pasting or modified usage. This can lead to an underestimation of AI influence.
📦 Sample Cursor Daily Record
Field
Value
date
2025-07-29
isActive
true
totalTabsShown
98
totalTabsAccepted
22
acceptedLinesAdded
105
acceptedLinesDeleted
16
composerRequests
6
composerSuggestionsAccepted
2
linesAdded
310
linesDeleted
48
This sample shows interactions for one day, with detailed metrics on suggestions shown, accepted, and the number of AI lines added by the developer.
FAQs
Q) Are Metrics Tied to Commits?
All four metrics (totalLinesAdded, totalLinesDeleted, acceptedLinesAdded, acceptedLinesDeleted) are based on editor activity. Cursor tracks changes as they happen in the editor, not when the code is committed or pushed. The "raw count of all code changes" refers to the actual edits made in the editor, regardless of whether those changes are later committed.
Q) If a user accepts an AI suggestion but later deletes the code or never commits/pushes it — does it still count in acceptedLinesAdded/Deleted for that day? Yes, if a user accepts an AI suggestion, it will be counted in acceptedLinesAdded/acceptedLinesDeleted for that day, even if the code is later deleted or never committed. These metrics track the initial acceptance of AI suggestions within the editor.
Last updated
Was this helpful?