# Agent analytics for Claude Code

_Published September 16, 2026_

**By [Eugenio Sanchez](https://mesmer.co/resources/author/eugenio)**

**Section:** Feature release

---

Mesmer now ingests coding-agent telemetry from **Claude Code**, and
reports it in a new **AI Usage** tab on the Metrics page. It answers a
question every engineering org is currently guessing at: what are the
agents costing, and what are they getting us?

### What the tab shows

- **Total AI spend**, **average spend per person**, **spend over
  [delivered effort](/resources/effort-recalibration)**, and **total
  tokens**.
- **Cost and token usage over time**, broken out by cost kind.
- **Top skills**, and who's using each.

Everything is scope-driven like the rest of Metrics: the same numbers at
organization, team, or single-person scope.

![The AI Usage tab in Mesmer, scoped to one organization over the last two weeks. Four KPI tiles read: Total AI spend $3,362.21 (all estimated, none provider-reported); Avg spend per person $305.66 across 11 people; Spend per 1,000 effort points $51.95, down 51%; Total tokens 4.3B, up 6% on the previous period. Below them, a 'Cost over time' bar chart of daily spend peaking near $500, a 'Token usage over time' chart of daily tokens peaking above 600M, and 'AI spend vs delivered effort' overlaying daily spend bars with delivered-effort and agent-assisted-effort lines that rise and fall together.](/blog/agent-analytics-tab.webp)

*Two weeks of agent spend for one organization, against the effort delivered in the same window.*

### Connecting Claude Code

Nothing to install, and nothing for your engineers to do. The AI Usage
tab starts empty with a single **Connect** on the Claude Code card, and
that's the whole entry point:

1. **Connect** takes you to **Settings → Integrations**. Connecting is
   admin-only — the connection is shared by everyone in the org.
2. Paste your **Claude organization ID**, which sits at the bottom of
   [claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization),
   and request a token.
3. Mesmer hands back a configuration block. Paste it as-is into
   **Managed Settings** at
   [claude.ai/admin-settings/claude-code](https://claude.ai/admin-settings/claude-code) —
   don't edit the snippet.

![Mesmer's Settings → Integrations page. Under 'Organization integrations' — shared by everyone in your organization, connectable only by admins — a Claude Code card titled 'AI coding usage and spend' reads 'Send Claude Code telemetry to Mesmer without changing the settings snippet we provide.' Below it, an 'Anthropic organization ID' field with a UUID placeholder, the hint 'In Claude Console, open your organization's Settings, then General, and copy its Organization ID', and a 'Request token' button.](/blog/agent-analytics-setup.webp)

*Step 2: paste the organization ID, request the token.*

That's it. Managed Settings pushes the change out for you, and Claude
Code may show each engineer a one-time notice that telemetry is being
collected. Data starts landing on its own.

---

Canonical: https://mesmer.co/resources/agent-analytics