> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cursor

> Connect Cursor to gain visibility into AI coding usage and admin activity

Glow's Cursor integration collects usage, analytics, and audit data for your Cursor team. It is a single connection authenticated with **one Cursor Admin API key** that grants access to all of the team admin endpoints.

| Data             | What it collects                                                                                                                           |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Team members** | Roster of team members with name, email, role, and removal status                                                                          |
| **Daily usage**  | Per-member daily activity — lines added/deleted, completions accepted, requests by type (chat, composer, agent), model, and client version |
| **Usage events** | Per-request events with timestamp, user, model, token counts, and request kind (included vs. usage-based)                                  |
| **Audit logs**   | Admin activity trail — member invites, role changes, and other team-management events with actor and IP address                            |

## Prerequisites

<Check>A Cursor team plan (Teams/Business) with **admin** access to the Cursor dashboard</Check>
<Check>A Cursor Admin API key (only team admins can create one)</Check>

## Setup Instructions

### Create the API Key

<Steps>
  <Step title="Open the Cursor dashboard as an admin">
    Log in to the [Cursor dashboard](https://cursor.com/dashboard) as a team **admin**. Only admins can mint Admin API keys.
  </Step>

  <Step title="Open the Admin API settings">
    Navigate to **Settings → Cursor Admin API**. See Cursor's [Admin API documentation](https://docs.cursor.com/account/teams/admin-api) for reference.
  </Step>

  <Step title="Create the key">
    Create a new Admin API key with a descriptive name (e.g., "Glow Integration"). The single key authorizes all of the team endpoints Glow reads (members, daily usage, usage events, audit logs).
  </Step>

  <Step title="Copy the key">
    Copy and securely store the key value. It is displayed only once.
  </Step>
</Steps>

### Complete the Integration

<Steps>
  <Step title="Provide the credential">
    Provide the API key to your Glow representative or enter it in the Glow console.
  </Step>

  <Step title="Connect in the Glow console">
    In the Glow console, open **Integrations → Cursor** and enter the API key in the connection drawer.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The connection fails with an HTTP 401 / unauthorized error">
    The Admin API key is invalid or has been revoked. Confirm you copied the full key value and that it has not been rotated in the Cursor dashboard. Re-mint the key under **Settings → Cursor Admin API** if needed.
  </Accordion>

  <Accordion title="Why is recent usage data missing?">
    Glow fetches daily usage and usage events over a rolling lookback window and re-fetches it each run to recover any late-arriving records. The most recent day may not be fully populated until Cursor finishes aggregating it.
  </Accordion>

  <Accordion title="The sync is slow or appears throttled">
    Cursor's Admin API is rate limited. Glow automatically backs off and retries (honoring the `Retry-After` header) when it hits the limit, so large teams may take longer to sync on the first run.
  </Accordion>
</AccordionGroup>