> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/features/ai-tools/cursor-activity.md).

# Cursor activity

See detailed Cursor activity patterns across teams and modes

Available at [AI tools → AI activity → Cursor](https://app.swarmia.com/ai/activity/cursor)

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FvyNQ3ahnGpVuFGYHHDqN%2F004058%402x.png?alt=media&amp;token=5065be01-da9b-4bb9-af70-29e0cf711940" alt=""><figcaption></figcaption></figure>

If you're looking for a productivity boost from Cursor, it's not enough to enable the tool for your teams and then forget it. People need to pick up the new habit and invest the time to learn how to use it effectively. To support that, you need proper visibility into the current activity patterns.

With the Cursor activity breakdown, you can:

* Understand where Cursor is gaining traction and where extra support may be needed.
* Know if people are just trying it out or actively relying on it in their work.
* Notice patterns in how suggestions are used across tab completions, agent, chat, and cmd+k.

Read more in our guide on [understanding the impact of AI tools](/guides/understand-the-impact-of-ai-tools.md).

To track Cursor adoption and licenses, see [AI adoption metrics](/features/ai-tools/ai-adoption.md).

## Setup

See our instructions for [enabling the Cursor integration](/settings/integrations/ai-coding-tool-integrations/cursor-integration.md).

## Definitions

* **Active users** = The number of users who have accepted code or used chat.
* **Code suggestions** = The number of Cursor code suggestions (excluding tab completions)
* **Code acceptances** = The number of Cursor code suggestions (excluding tab completions) accepted by users
* **Acceptance rate (suggestions)** = *Code acceptances / Code suggestions*
* Chat requests:

  * **Agent** = Requests in the chat using the "Agent" mode
  * **Ask** = Requests in the chat using the "Ask" mode
  * **CMD+K** = "Quick Edit" inline edits (⌘K on Mac)
  * **Composer** = Cursor's legacy multi-file edit feature

  <figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2FnR2qN9JSHXordFbplavt%2Fimage.png?alt=media&amp;token=fe6f942e-f0cf-4724-8574-beec23ef5ea8" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Not all accepted code ends up in the codebase. An engineer could accept 200 Cursor-generated lines over the course of creating a 10-line pull request.

You can't use these metrics to get an accurate number of the share of your code that's AI-generated.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/features/ai-tools/cursor-activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.