Skip to main content

Configuring Cursor

LinearB connects with Cursor to measure conversational coding activity, from chat requests to code completions. Admins can configure the integration in Settings with a personal access token, allowing Cursor adoption and usage metrics to appear in AI Insights.

Steven Silverstone
Updated by Steven Silverstone

LinearB integrates with Cursor to track adoption, request activity, and acceptance metrics for conversational coding. This integration helps you understand how developers are using Cursor’s AI capabilities—such as code suggestions, chat requests, and automated agents—and what impact they have on your workflow.

Admins can configure Cursor in Settings > Company Settings > AI Tools > Cursor by providing a personal access token (PAT). Once connected, usage data appears in AI Insights.

Overview

Cursor metrics allow you to:

  • Track active and engaged users across your teams.
  • Measure AI-assisted requests, including chat, agent, and composer activity.
  • Monitor code suggestions generated by Cursor and how many are accepted.
  • Evaluate Cursor’s overall contribution to the codebase.

This data feeds directly into the AI Tools Usage and AI Adoption widgets in AI Insights.

Setup Steps

  1. In the LinearB sidebar, go to Settings > Company Settings > AI Tools > Cursor.
  2. Generate a Cursor Personal Access Token (PAT) with the required scopes.
  3. Paste the token into the Token field.
  4. Click Save.
  5. Verify the connection shows as Connected with the last updated date.

Metrics

Once connected, the following metrics are available in AI Insights:

  • Active Users — Average number of developers using Cursor per day.
  • Engaged Users — Developers actively accepting AI suggestions per day.
  • Code Tabs Suggested — Average number of AI-generated code blocks suggested per day.
  • Code Tabs Accepted — Average number of suggested code blocks accepted per day.
  • Code Acceptances — Average number of accepted AI completions per day.
  • Code Lines Accepted — Number of AI-suggested lines accepted per day.
  • Agent Requests — Average number of AI agent requests per day.
  • Composer Requests — Average number of AI-assisted composer requests per day.
  • Chat Requests — Average number of chat-based AI requests per day.
  • CMDK Requests — Average number of Cursor CMDK (command kit) requests per day.

Verify in AI Insights

Once enabled, Cursor activity appears in:

  • AI Tools Usage — Adoption trends, request types, and code acceptance metrics.
  • AI Adoption — Cursor’s contributions alongside Copilot and LinearB AI.

Troubleshooting

If Cursor data does not appear in AI Insights:

How did we do?

Contact