Cursor cost and usage visibility
Cursor does not export per-session telemetry the way Claude Code and Codex do, so we will not pretend it does. There are two real ways to see Cursor in Acticly, and which one fits depends on whether your traffic runs through a gateway.
What Acticly reads
- Through a LiteLLM gateway: billed spend for Cursor traffic, attributed per person.
- Without a gateway: commit messages, pull request metadata, Co-Authored-By trailers, branch prefixes such as `cursor/`, and labels.
What you get
- With a gateway — per-person Cursor spend, totalled with your other AI cost, and the same alerts and controls as any other source.
- Without a gateway — which commits and pull requests were Cursor-assisted, who is adopting it, and how that tracks against delivery. No setup, no config file, nothing for developers to do.
How to connect
Nothing to install either way. For spend, point Cursor at a LiteLLM gateway and connect that gateway to Acticly. For adoption and commit visibility, connect your code repository — detection is automatic.
Two paths, pick what matches your setup
Spend Cursor → LiteLLM gateway → Acticly pulls billed spend
(one admin setup, per-person attribution)
Adoption Connect GitHub / GitLab / Bitbucket
(zero setup — Cursor-assisted commits detected automatically)What this does not cover
- Per-session Cursor telemetry. Cursor does not export it, and no configuration on our side changes that.
- Spend for Cursor traffic that does not pass through a gateway — there is no billing signal for us to read.
- Prompt or completion content, on either path.