Skip to content
Menu

Guides

How to see what your team spends on Claude Code, and who is using it

Checked on 3 November 2026 against the sources below.

What you can see depends on how your team pays for Claude Code. On a Claude Team or Enterprise plan, an Owner sees adoption at claude.ai/analytics/claude-code, with daily active users, sessions and lines of code accepted, and, once usage credits are turned on, a spend report of what each member spent past their seat, by user and by model, a day behind. Usage inside the seat allowance is not metered in dollars, so the rest of the cost is simply the seat price times the seats. If your team uses Claude Code through the API, the Claude Console dashboard shows estimated spend per member. If your engineers are on their own Max or Pro plans paid on company cards, Anthropic has no team view at all. OpenReason Intel gives one view whichever way the team pays: one command on each engineer's machine, and a dashboard that shows seat commitments and variable spending together, per person, with who is active and who is idle, and what each person's usage went into by repo and pull request.

Each case is set out below with the vendor pages it was checked against, then what OpenReason adds and what it does not do.

On a Claude Team or Enterprise plan

Two screens, for two different questions. For who is using it, the Claude Code analytics dashboard at claude.ai/analytics/claude-code, which Admins and Owners can open, shows "lines of code accepted, suggestion accept rate, daily active users and sessions", a leaderboard of the top ten users by contribution, and, with the GitHub app connected, how many merged pull requests contained Claude Code's work. Contribution data exports as a CSV for all users.

For what it costs, the usage analytics page in your organisation's settings has a spend report, which Team plan Owners and Primary Owners can open. The CSV lists each user's email, the model, request count, prompt and completion tokens, and net spend. "Spend data refreshes daily and has a one-day delay." The Claude Code docs add the limit that matters: the report "covers usage-credit spend and appears once usage credits are turned on. Usage inside the seat allowance isn't metered in dollars." So a team that has never turned usage credits on has no dollar figure per person, because nobody has spent anything past their seat.

The seat part of the bill is arithmetic from claude.com/pricing: a Standard seat is $25 a member a month, or $20 billed annually, and a Premium seat is $125, or $100 annually. As an example, twelve engineers on Standard seats billed monthly cost 12 × $25 = $300 a month before any usage credits. Anthropic's pages do not say how much Claude Code a seat holds beyond "more usage than Pro" for Standard and "5x more usage than standard seats" for Premium.

What neither screen shows: how far each member is through their 5-hour or weekly window, which sessions or repos the usage went into, or what a pull request cost. On the Enterprise plan the Enterprise Analytics API returns per-user usage and cost reports; the docs say it "is not available on the Teams plan".

On the API through the Claude Console

If your engineers sign in to Claude Code with a Console account, every token is billed to your organisation, and the Console dashboard at platform.claude.com/claude-code shows "lines of code accepted", "suggestion accept rate", active users and sessions, and spend as "daily API costs in dollars". Its team insights table lists each member with their spend and lines accepted for the date range you pick. The docs note that these spend figures "are estimates for analytics purposes" and point to the Cost page for actual costs. You can cap spend with a workspace spend limit, and pull daily per-user figures with the Claude Code Analytics API.

On individual Max or Pro plans the company pays for

A lot of teams started this way: each engineer has a Max plan on a company card. Anthropic treats each as an individual. The Claude Code docs: "On an individual Pro, Max, or Ultra plan you have no organization to manage". Each person sees their own usage under Settings > Usage on claude.ai and their own usage-credit spend in /usage; nobody else does. The company's record of the spend is the card statement, and the only way to know who is using the tool is to ask.

Which engineers are actually using it

Anthropic answers this with counts: daily active users and sessions on the Team dashboard, active users on the Console dashboard, and the leaderboard's top ten. What the counts do not give you is the seat you are paying for that nobody has opened in a month, or the person with a Premium seat who uses it like a Standard one. For that you need a list of people against their seats and their activity, which is the view below.

See it in one place with OpenReason Intel

OpenReason Intel is built for this question. Each engineer runs one command on their machine, from the or-otel quickstart, which configures Claude Code and Codex to report to OpenReason over OpenTelemetry and installs a small reporter. Their requests still go straight to Anthropic and OpenAI on your own plans; OpenReason is not a proxy. The reporter sends tokens, model, session length, the repo, the commands the agent ran, each person's plan and their 5-hour and weekly limits, and by default the text of prompts and replies, which the team lead chooses whether to keep; --no-log-prompts at install stops a machine sending text at all.

What you then see, in the words the product uses:

  • Spend: seat commitments and variable spending together, with vendor totals, and Claude usage-credit spend beside Codex credits. A figure is marked as vendor-reported, allocated from a vendor amount, or estimated at list price, because they are not the same thing, and the view is not a reconciled invoice.
  • People: each person against their seat, with their usage and quota activity, active days, over-limit incidents and spending. Idle seats are the ones with no activity against them.
  • Work: branch and feature activity alongside agent time, turns, quota, overage and the recorded commits and pull requests, so you can see what the usage went into. A missing pull request does not mean no useful work was done, and a pull request is not a measure of value.

It is the same view whether the team is on Team seats, on the API or on a dozen Max plans, because the figures come from each machine rather than from the vendor's billing. Claude usage-credit spend is exact when the team turns on the option that lets or-otel ask Anthropic for each person's figure with their own Claude Code sign-in; otherwise it is allocated or estimated and labelled so. Each engineer sees the same things about themselves and nothing about a teammate.

Two things to be clear about. It does not set budgets, warn anyone or stop a request; it shows you what happened so you can look into it, and because the data is on each machine and in the dashboard, a team with a coding agent can build its own warning on top. And it is evidence for a conversation, not a verdict on a person: a high figure beside a name is a reason to ask what the work was, which the Work view is there to answer. It is free for teams under ten engineers and $20 an engineer a month after that, on the pricing page; sign-up takes an email address or a Google account, no card. Today it reports Claude Code and Codex.

What to do next

  1. Read next

  2. See what used up your limit

    Session Forensics is a free page that reads the Claude Code and Codex session files already on your computer, in your browser. It lists the limits you hit and the turns that used each one up. There is nothing to install and no sign-up, and your files are never uploaded. For Claude Code its 5-hour figure is an estimate, because Claude Code's files do not record the meter.

    Would you rather have your own agent do it? Paste this prompt into Claude Code or Codex.

    Open Session Forensics (opens in a new tab)

  3. Get an email when the limits change

    Get an email when Claude Code or Codex limits change. One email per change, at most one a week, from OpenReason. Unsubscribe from any email in one click.

  4. Track it over time

    OpenReason Intel keeps a record of your Claude Code and Codex 5-hour and weekly windows from every machine you use, with each turn's estimated share of the window and what it cost once the window was full. It is free for small teams: sign up with Google, no card, then run one command on Mac, Windows or Linux.

    It shows you what happened; it does not stop a session as you work, and it cannot change your vendor's limits.

    Sign up free with Google

Questions people ask

How do I see what my team spends on Claude Code?
On a Team or Enterprise plan, an Owner opens the spend report in the organisation's usage analytics, which lists usage-credit spend per user and model a day behind; the seat cost is the seat price times seats, since usage inside the seat is not metered in dollars. On the API, the Console dashboard shows estimated spend per member. On individual Max plans there is no team view. OpenReason shows seat commitments and variable spending together per person whichever way you pay.
How do I see which engineers are actually using the AI tools we pay for?
Anthropic's Team dashboard shows daily active users, sessions and a leaderboard; the Console dashboard shows active users and spend per member. OpenReason's People view lists each person against their seat with their active days, usage and quota activity, so an idle seat is a row with nothing against it.
How do I find out who on my team went past their plan and what it cost?
On a Team plan, only members with usage credits turned on can go past their seat, and the Owner sees each member's month-to-date usage-credit spend in the organisation's usage settings and the spend report. OpenReason shows each over-limit period with the person, session, repo and model around it, and what it cost with the figure's qualifier. The guide on who went past their plan has the detail.
How do I manage overages on Claude Team or Max plans for a team?
On a Team plan an Owner turns usage credits on and sets a monthly spend limit for the organisation and for each member; with credits off, a member who hits a limit simply stops. On Max plans each person manages their own credits and limit, and the company sees only the card statement. OpenReason shows the 5-hour and weekly history per person and the turns around each over-limit period, so you can see what the overage bought.

Sources

Every figure on this page was read from these pages on 3 November 2026. Limits and prices change; if a vendor page now says something different, the vendor page is right and this one is out of date.