The Cursor integration connects your Cursor team to 15Five AI, bringing in adoption and usage signals from Cursor, the AI code editor, so you can understand how your engineers are using it and where it is driving impact.
Teams or Enterprise only. The integration reads usage data through Cursor's Admin API using a read-only key, which is available only to organizations on a Cursor Teams or Enterprise plan. If your organization is on an individual plan, the integration cannot be connected.
Available now: connect and sync. Coming soon: insights. You can connect Cursor and start syncing usage today. Putting that data to work in 15Five AI's briefs and AI-assisted reviews is rolling out next.
Note: To ensure the highest level of security, 15Five is continually investing in our overall information security program, resources, and expertise. To review 15Five's security documents, and how we handle your company data, see our Trust Website.
Access and Availability
| Role | Requirement |
|---|---|
| Cursor team admin | Required to open the Cursor dashboard and create a read-only Team API key |
| 15Five Company Admin, HR Admin, or IT Admin | Required to supply the key and complete the connection in 15Five |
The same person can hold both roles, or two people can coordinate the install.
What It Enables
- Measures Cursor adoption across your engineering organization, including who has not adopted it yet and how adoption grows over time.
- Shows engagement depth across Cursor's AI surfaces.
- Shows how much AI-suggested code was produced and how much was kept.
How Access Works
15Five AI connects with a single Team API key set to Cursor's Read-only scope, the scope Cursor provides for usage and member analytics. There is no per-engineer login. That one key defines everything 15Five AI can see.
Usage signals only, never your code or prompts. The integration reads usage statistics from Cursor's Admin API: how much each member used Cursor and how they engaged with its features. Your source code, file contents, prompts, and the contents of Cursor conversations are never read. The most detail it sees about what someone worked on is an aggregate count and the most-used file extension, for example ts, never file names, paths, or contents.
Because everything flows through this one key, it is your control point. You can revoke it from the Cursor dashboard at any time, and 15Five AI's view stops at whatever the key can read.
Permissions Overview
| Key | Scope in Cursor | What 15Five AI uses it for |
|---|---|---|
| Team API key | Read-only (usage and member analytics) | Fetch per-user, per-day usage and code-activity metrics from Cursor's Admin API |
The Read-only scope cannot create, modify, or delete anything in your Cursor team. Cursor also offers an Admin scope for full Admin API access. The integration does not require it and does not use it.
What Gets Synced
Cursor reports usage per person, per day, through its Admin API.
Cursor users
Daily activity is attributed to each team member referenced in your Cursor usage data, by Cursor user ID and work email.
Usage activity (per user, per day)
- Requests by surface: Agent, Chat, Composer, Cmd-K, and Tab.
- Included vs. usage-based requests: volume covered by your plan vs. overage, plus Bugbot requests.
- Tab suggestions: how many inline completions were shown versus accepted.
- Active status and client version: whether the member was active that day, and the Cursor version they were on.
Code activity (per user, per day)
- Lines added and removed, and lines accepted: the volume suggested and how much was kept.
- Applies, accepts, and rejects: how often suggestions were applied, accepted, or rejected.
- Most-used file extensions: for example the top extension for applies and for Tab, such as ts. This is the file extension only, never file names, paths, or contents.
Backfill and sync cadence
On first connect, up to 12 months of history is backfilled. Actual depth depends on retention settings and permissions in the source system, so some accounts may see less. After the initial backfill, each run pulls the latest available days from Cursor's Admin API on an ongoing basis.
Connected data is processed to generate insights, patterns, and trends rather than kept as a raw log, and the underlying raw content is not retained after 30 days.
What Does Not Get Synced
- Source code, file contents, and diffs
- Prompts and the contents of Cursor conversations
- File names and file paths
Key Rules
- A Cursor Teams or Enterprise plan is required. Cursor's Admin API is not available on individual plans.
- The integration uses one Team API key set to Read-only. The Admin scope is neither requested nor used.
- Usage signals only. Code, prompts, and conversation contents are never read.
- Connect and sync are available now. Use of Cursor data in briefs and AI-assisted reviews is still rolling out.
- Revoking the key in Cursor stops what 15Five AI can read. Deleted keys cannot be restored, so reconnecting means creating a new read-only Team API key.
Common Questions
Does 15Five AI read our source code or prompts?
No. The integration reads usage statistics only. Source code, file contents, prompts, and Cursor conversation contents are never read.
Can the integration change anything in Cursor?
No. The Team API key uses Cursor's Read-only scope, which cannot create, modify, or delete anything in your Cursor team.
Do we need the Admin scope?
No. Read-only is the scope Cursor provides for usage and member analytics, and it is the only scope the integration uses.
How much historical data is imported?
Up to 12 months of history is backfilled on first connect. Actual depth depends on retention settings and permissions in Cursor, so some accounts may see less.
Why can I connect Cursor but not see insights yet?
Connecting and syncing are available now. Using that data in briefs and AI-assisted reviews is rolling out next.