Connect Claude Code

Claude Code usage appears beside delivery as context: who's using it, how much, and what it costs. It's never a score. There are two ways to connect it, depending on how your developers pay for Claude.

Which way is yours?

One is enough. If a developer's usage arrives both ways, we combine it per person and day, so nothing is counted twice.

Team or Pro: telemetry

Claude Code can report usage counts as it runs. On Connections, the Claude Code (telemetry) card has a Settings for each developer block with your workspace's own token in it. Each developer:

1. Opens ~/.claude/settings.json (creating it if it isn't there).
2. Pastes the block inside the file's outer braces. If the file already has an "env" section, they add the lines to it instead.
3. Starts a new Claude Code session. Sessions that were already open don't pick up the change.

It sends usage counts and the developer's Claude login email only: sessions, lines added and removed, edits accepted and rejected, tokens and estimated cost. Never prompts, responses, file contents or file paths.

Share the block privately, for example in your password manager or a direct message. The token is your workspace's alone; anyone with it could send usage into your workspace.

To roll it out to many machines at once, your IT team can put the same env block in Claude Code's managed settings instead.

Claude Console: Admin API key

1. An admin of your Claude Console organization opens Settings → Admin keys and creates a key. It starts with sk-ant-admin01-.
2. On Connections, paste it into the Claude Code (Admin API) card and press Connect. It's stored encrypted.

Usage then arrives with the nightly sync, one day at a time per person.

Checking one machine works

Have one developer set up telemetry, start a new session and use Claude Code for a few minutes. Within 15 minutes the telemetry card changes from “Waiting for first data” to “Receiving data”, with the date of the latest. Then roll it out to everyone else.

If nothing arrives after 30 minutes, check that:

• the developer started a new session after saving the file;
• the file is still valid JSON (a missing comma is the usual culprit);
• the token in the file matches the one on the card, with nothing cut off when copying.

Matching usage to people

Usage is matched to people by their Claude login email. If someone signs in to Claude with a different email from the one in Jira or GitHub, they'll show up as a separate person to merge; see People, identities and teams. Someone outside engineering who uses Claude Code, a VP with a seat say, can be marked “Outside engineering” so their usage stays out of your engineering numbers.