Critical Data Anomaly in Cursor API - Acceptance Rate Exceeds 200%

[user546]

Describe the Bug

Dear Cursor Technical Support Team,
We have identified a critical data anomaly in your daily usage data API (https://api.cursor.com/teams/daily-usage-data) for August 18-19, 2025.
Issue Description:
The accepted AI code lines (acceptedLinesAdded + acceptedLinesDeleted) are significantly greater than the AI suggested code lines (totalLinesAdded + totalLinesDeleted), resulting in acceptance rates exceeding 200%, which violates basic business logic.
Evidence:
August 18: 186.80% acceptance rate (72,732 suggested vs 135,864 accepted)
August 19: 206.07% acceptance rate (74,449 suggested vs 153,420 accepted)
94 affected users (8.6% of total users)
One of our member even shows 78,566.7% anomaly ratio!

Please help us and fix this issue

Steps to Reproduce

Bug Description
Critical Data Anomaly: Acceptance Rate Exceeds 200% in Daily Usage Data API
The Cursor API returns acceptance data that violates basic business logic, where accepted AI code lines exceed suggested AI code lines, resulting in impossible acceptance rates.
Environment
API Endpoint: https://api.cursor.com/teams/daily-usage-data
Authentication: Team API Key
Date Range: August 18-19, 2025
Data Fields: totalLinesAdded, totalLinesDeleted, acceptedLinesAdded, acceptedLinesDeleted

Step 1: API Authentication Setup
Obtain a valid Team API Key from Cursor
Set up authentication headers

Step 2: Request Data for August 18-19, 2025
Convert dates to UTC milliseconds epoch timestamps:
Start: August 18, 2025 00:00:00 CST → UTC timestamp
End: August 19, 2025 23:59:59 CST → UTC timestamp

Step 3: Analyze Response Data
Extract the data array from the API response
Filter records for specific dates (August 18-19)
Calculate for each user:
Suggested lines: totalLinesAdded + totalLinesDeleted
Accepted lines: acceptedLinesAdded + acceptedLinesDeleted
Acceptance rate: (accepted lines / suggested lines) × 100%

Step 4: Identify Anomalies
Look for users where accepted lines > suggested lines
Calculate overflow: accepted lines - suggested lines
Identify users with acceptance rates > 100%

xpected Behavior
Acceptance rate should always be ≤ 100%
acceptedLinesAdded ≤ totalLinesAdded
acceptedLinesDeleted ≤ totalLinesDeleted
Users cannot accept more lines than what AI suggested
Actual Behavior (Bug)
Acceptance rates exceed 200%
Many users show accepted lines > suggested lines
Some users have acceptance rates over 10,000%

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5 (Universal)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[dewu]

Our team is experiencing the same issue, which mainly manifests in the following scenarios:

• acceptedLinesAdded > 0, yet totalLinesAdded = 0

• There are multiple agentRequests, and in actual usage we accept changes several times, but acceptedLinesAdded in the statistics remains 0.

异常数据如下：

{
  date: 1756166400000,
  userId: "user_xxxxxx",
  email: "xxxxx",
  isActive: true,
  totalLinesAdded: 0,
  totalLinesDeleted: 0,
  acceptedLinesAdded: 1631,
  acceptedLinesDeleted: 99,
  totalApplies: 31,
  totalAccepts: 31,
  totalRejects: 0,
  totalTabsShown: 3,
  totalTabsAccepted: 0,
  composerRequests: 0,
  chatRequests: 0,
  agentRequests: 8,
  cmdkUsages: 0,
  subscriptionIncludedReqs: 8,
  apiKeyReqs: 0,
  usageBasedReqs: 0,
  bugbotUsages: 0,
  mostUsedModel: "claude-4-sonnet-thinking",
  applyMostUsedExtension: "go",
  tabMostUsedExtension: "go",
  clientVersion: "1.5.5",
}

{
  date: 1756080000000,
  userId: "user_xxxxxx",
  email: "xxxxx",
  isActive: true,
  totalLinesAdded: 0,
  totalLinesDeleted: 0,
  acceptedLinesAdded: 0,
  acceptedLinesDeleted: 0,
  totalApplies: 0,
  totalAccepts: 0,
  totalRejects: 0,
  totalTabsShown: 16,
  totalTabsAccepted: 0,
  composerRequests: 0,
  chatRequests: 0,
  agentRequests: 9,
  cmdkUsages: 0,
  subscriptionIncludedReqs: 9,
  apiKeyReqs: 0,
  usageBasedReqs: 0,
  bugbotUsages: 0,
  mostUsedModel: "claude-4-sonnet-thinking",
  tabMostUsedExtension: "go",
  clientVersion: "1.4.5",
}

This problem is currently causing considerable trouble for our team, and we sincerely hope to receive assistance from the official team. @danperks

[condor]

hi @user546 @dewu thank you for your reports. Please let me know which Cursor version your team members are using.

• We are rolling out improved tracking for lines of code generated and accepted, which will give you much more accurate metrics.

• A new “v2” for four key metrics has been developed:

  • Total Accepted Lines (in Cursor 1.4)
  • Total Suggested Lines (telemetry comes in Cursor 1.5, early September)
  • File Extensions (new approach in Cursor 1.4)
  • Client Version (new approach in Cursor 1.4)

The new solution is more accurate and explains the noticeable jump in Accepted Lines for many users (sometimes 3-4x higher compared to before).

Suggested Lines, Accepted Lines, file extension data, and client version are all now measured more robustly. You’ll see lineage and sources for diffs as well.

[user572]

The returned data contains timestamps earlier than the input startDate. Could you please help check this? When I request data for a specific day, the response includes both that day’s data and the previous day’s data.

[dewu]

@condor

新的解决方案更加准确，并解释了许多用户接受的线路的明显跳跃（有时与以前相比高出 3-4 倍）。

Suggested Lines, Accepted Lines, file extension data, and client version are all now measured more robustly. You’ll s

@condor Based on usage data, most versions of our team are within the range of v1.2 to v1.5.

[condor]

@dewu for accurate details they would have to be at least on 1.4 but if you need also suggested lines then 1.5.

@user572 I will check with the team and update you.

[user572]

should not zero

[VimZZ]

Total Suggested Lines (telemetry comes in Cursor 1.5, early September)

When is expected to be released?

[condor]

hi @VimZZ Cursor 1.5 is the current stable release.

We are already launching 1.6 in beta today.

[VimZZ]

@VimZZ

Total Suggested Lines

Thank you @condor - where can I see the API docs for Total Suggested Lines ? We try to use totalLinesAdded to calculate acceptance rate but encounter the issues other users mentioned and I am looking what’s the best way to achieve that

[condor]

hi @VimZZ here is the docs page that tracks total suggested lines, it should jump to that section and you can there alternatively search for the word suggested with CMD/CTRL+F

Cursor – Admin API

[VimZZ]

Thank you again but I dont think I found it

What I see is acceptedLinesAdded and acceptedLinesDeleted which together are totalAcceptedLines, but I can’t see how I can get totalSuggestedLines, like you mentioned earlier. As totalAccepts and totalRejects are not counting lines and as other reported doesnt make sense when compared (as others users reported we see 98% acceptance rate which doesn’t make sense)

[VimZZ]

@condor have you seen my last question? can you help please?

[condor]

Yes checking with the team about it.

[condor]

@VimZZ the Total Suggested Lines are in the Dashboard and currently not in the API as separate value. I have forwarded the feedback to the team.

However the acceptedLinesAdded + acceptedLinesDeleted would show the total suggested lines.