Cursor Integration

Connecting Cursor lets Koalr track AI coding assistant adoption across your team — who is using Cursor, how often, which models they use, and how spend is distributed.

What Koalr syncs

• Daily Active Users (DAU) — how many team members used Cursor each day (30-day trend)
• Total requests — aggregate AI request count per day
• Model usage breakdown — distribution across claude-3-5-sonnet, gpt-4o, cursor-small, and others
• Per-member spend — individual usage costs (visible to Admins only; hidden from individual members by default)
• Team spend — total monthly AI spend, trended

Prerequisites

• Cursor Team or Business plan (Enterprise plan required for full Analytics API access)
• Cursor team Admin role to generate an API key
• API key generated at: Cursor Settings → Team → API Keys

Setup

1. In Koalr, go to Settings → Integrations → AI Tools.
2. Click Connect next to Cursor.
3. Paste your Cursor API key.
4. Enter your Cursor team ID (visible in the URL at cursor.com/settings/team/[team-id]).
5. Click Save. Koalr syncs the past 30 days of usage data immediately.

AI Analytics dashboard

After connecting, Cursor data appears in AI Analytics (/ai-analytics):

• Cursor DAU trend — 30-day daily active users chart
• Top models — which Cursor models your team uses most
• Total requests — daily request volume trend
• Per-member activity — individual adoption (Admin view)
• Spend — total and per-member cost (Admin view)

This dashboard also shows GitHub Copilot data side-by-side if that integration is connected.

Privacy and visibility

• Individual member spend and request counts are only visible to Admins
• Engineers see only aggregate team metrics in their own view
• No prompt content or code is ever accessed — Koalr reads only usage metadata from the Cursor API

Troubleshooting

"Insufficient plan" error: The full Analytics API (DAU, model breakdown, spend) requires Cursor Business or Enterprise. The Team plan provides basic member list only.

Data showing 0 after connecting: Cursor's API has up to a 24-hour delay before usage data appears. Check again the following day. If the issue persists, verify the API key hasn't been rotated.