How do you see Claude Code usage per developer?

In one of three ways, each reading a different source:

A laptop tracker shows what one person used, and only on the machine it runs on. A key per developer shows who spent what, but leaves a list of keys to go through whenever somebody leaves. Subscription seats are not billed per token, so their traffic is missing from any per-key bill.

Each source covers one tool or one kind of money. A total per person ends up as a spreadsheet that somebody joins by hand.

With Selan, each developer signs in once, as themselves, with selan login. selan claude then runs Claude Code on the company's accounts and selan codex runs Codex, while Claude Desktop joins with one settings file. Every request is recorded with who ran it, which account served it, which model answered and what it cost.

The launch commands are in the docs, and the Codex and Desktop setups in Codex and Claude Desktop. For Codex on its own, with what OpenAI's analytics show, see how to track Codex CLI usage.

Usage, in the Selan control app, covers the last 24 hours, 7 days or 30 days, in UTC. Its tiles give the window's API bill and cache hits, and either its total cost or its new tokens, whichever the page is measured in. New tokens leave out cache reads, so a long conversation does not look like more work than it was.

A ranked list orders people by new tokens or by cost, with each one's share of the window. Click a name and the whole page narrows to that person. Charts split the same window by provider, by model and by client, so Claude Code, Codex and Claude Desktop each get their own band.

A subscription seat is priced at what the same requests would have cost per token, next to what your pay-per-use keys actually cost. A request that cannot be priced shows as unknown, never as zero.

Yes. An owner puts each person in one team, and Usage ranks teams beside people. It can also narrow to a single team, and every figure on the page follows. A team's figure is its people's figures added up, so the two lists cannot disagree.

Teams are for reporting only: a team grants nothing and caps nothing. A CI job's API token spends under an address of its own and belongs to no team, so the jobs show up as themselves.

Their own, yes. Usage is the owner's view, and a developer never sees anybody else's numbers. Each developer's spend against their own limit is on the statusline Selan adds to Claude Code. selan usage prints the same numbers without launching Claude Code, which is how a Codex user reads them.

What the statusline shows is in the statusline docs, and the command in the reference.

Tracking tells you who spent too much after they have spent it. In Selan you can set a spend limit per person, by day, week or month, and it follows them across every pay-per-use key you added. A limit binds the moment it is reached, and the refusal says which limit it was and when it lifts.

Which repository the time went to is a separate switch, off until an owner turns it on. Limits are on the spend page, and repositories on the insights page.

Free for up to three seats, and the Free plan needs no card.