> 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

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

<figure><img src="/files/vqP8Vvq9pPIrHK4RJnbF" 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="/files/yj665yCYXulvBwGJ6xnd" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.