Can I see Cursor spend per developer?

Yes. Cursor's team dashboard shows usage and spending across team members on the Teams and Enterprise plans. It does not break spend down by git repository or pull request.

Can Cursor show spend per repository or client?

Not on the team dashboard. Cursor's AI Code Tracking API reports per-commit AI usage, and it is an Enterprise feature. To get spend per repo on any plan, capture each agent turn with its git context. PromptConduit's Cursor hooks do this and roll it up per repo, pull request, and client.

Can I set a Cursor budget per repository?

Cursor's settings set a monthly team spending limit, and per-member limits are Enterprise-only. PromptConduit budgets are alerts rather than hard stops: set a monthly amount for the whole team, a repository, or a member, and owners and admins get an email and a Slack post at 80% and 100%.

Will the totals match my Cursor invoice?

No. PromptConduit prices each turn at public API rates from the token counts Cursor's hooks report. It does not know whether a request used included or on-demand usage, and it does not add the Cursor Token Rate on Teams and Enterprise. Use it to see where spend goes, and the invoice for what you owe.

Tracking on your own machine is free. Team dashboards are free for up to 3 members, $99 per month flat for up to 15, and $249 per month for up to 50.

Cursor Expense Tracker for Teams: Spend per Developer, Repo, and Client

Cursor’s team dashboard tells you how much the team spent and which members used the most. It does not tell you which repository, pull request, or client the money went to, and that is usually the question a finance review asks. To answer it, record each Cursor agent turn with its token counts, model, and git context, then total it per repo, PR, and client. PromptConduit does this with Cursor’s hooks and adds monthly budgets with email and Slack alerts.

This guide covers what Cursor gives you, where the gaps are, and how to set up a per-repo, per-client Cursor expense report for a team.

What Cursor’s dashboard covers

Per Cursor’s team dashboard docs, checked on 2026-10-25:

Question	Cursor team dashboard	Plan
How much did the team spend this cycle?	Yes, usage and spending	Teams, Enterprise
Which members used the most?	Yes, per-member activity	Teams, Enterprise
Cap total team spend	Yes, monthly team spending limit	Teams, Enterprise
Cap one member’s spend	Yes, per-member limits	Enterprise only
Spend per git repository	No	n/a
AI usage per commit	AI Code Tracking API	Enterprise only
Spend per pull request or client	No	n/a
Claude Code, Codex, or Gemini CLI in the same report	No	n/a

For a team below Enterprise, this means member totals are covered, and everything tied to the code itself is not.

Track Cursor spend per repo, PR, and client

1. Each developer installs the CLI and the Cursor hooks.

curl -fsSL https://promptconduit.dev/install | bash
promptconduit install cursor

This adds hooks to ~/.cursor/hooks.json. Each agent turn is priced on the developer’s machine from the token counts in the hook payload, tagged with the workspace’s repo, branch, and commit, and written to a local log first.

2. Each developer signs in and joins the team.

promptconduit init

Create the team at app.promptconduit.dev/team and invite each member; the team page gives you an accept link to share with them. Events sync with the member’s own API key, so spend is attributed to whoever ran the turn.

3. Open the team page. Cost is broken down by member, model, repository, branch, pull request, and day. A turn on a branch with an open pull request counts toward that PR.

4. Tag repositories with clients. If you bill clients, tag each repository with the client it belongs to, and the team page totals spend per client. See the agencies page.

5. Export the expense report. Export CSV on the team page downloads the period’s cost grouped by client, repository, pull request, member, or day.

Budgets and alerts

Set a monthly budget for the whole team, one repository, or one member under Budgets on the team page. Each budget shows month-to-date spend and where the month will end at the current pace. When a budget reaches 80% and again at 100%, owners and admins get an email, and the alert also posts to a Slack channel if you connect an incoming webhook.

These budgets alert rather than block. Cursor’s own spending limit is still the hard stop.

Common pitfalls

Invoice numbers. Costs are API-equivalent. Included usage, on-demand usage, and the $0.25 per million token Cursor Token Rate on Teams and Enterprise are not modeled.
Shared keys. Attribution follows the API key. If two developers sync with one key, their spend merges into one member.
Multi-root workspaces. Spend lands on the first folder in the hook’s workspace_roots.
Folders without git. A turn outside a git repo still counts per member and model, with no repository.
Undocumented token fields. Cursor’s hooks reference does not list the token fields yet. A payload without token counts produces no cost.

For the single-developer version of this, with a jq recipe over the local log and how to read each token column, see Cursor AI spend by repo and model.

Claude Code and other tools in the same report

Most teams don’t run Cursor alone. The same CLI captures Claude Code, Codex, Gemini CLI, Copilot, and Grok Build, all priced the same way, so the per-repo total covers every tool. Claude Code can also send cost with nothing to install through its built-in OpenTelemetry export; see Claude Code OpenTelemetry cost tracking. For the whole picture across tools, read how to attribute AI coding spend to teams and repos.

Teams of up to 3 are free. Team is $99 per month flat for up to 15 members, and Growth is $249 per month for up to 50. See pricing.