How your teams use Claude Code,session by session.
Tokens, tool calls, errors and the git branch behind every Claude Code session run in Claude Desktop, alongside billed spend per person. Ask for it in the dashboard, or ask Claude itself through MCP.
Everyone has Claude Code.Nobody has the picture.
01
Adoption is anecdotal
You hear who loves it and who gave up, but not how it's used across the team.
02
Failures are invisible
Tool errors and abandoned sessions don't show up anywhere a lead can see them.
03
Spend arrives as one number
The invoice rises without telling you which work drove it.
Scenarios
Questions engineering leads ask,with the data to answer them.
How OpenWatch answers
Every session records the git branch and working directory it ran in, so usage maps onto real codebases rather than guesses.
How OpenWatch answers
Open its audit trail to see tool calls, errors, rate limits and results in order, with token counts on each message.
How OpenWatch answers
Billed spend from Anthropic's Analytics API, split by person and by product, with trends by day or week.
What engineering leads get.
- Usage mapped to codeGit branch and working directory on every session.
- Errors surfacedTool errors flagged on sessions so struggling workflows stand out.
- Spend per personBilled usage split across Claude Code, Cowork and chat.
- Answers from ClaudeThe MCP server lets Claude answer usage questions from the same data.
Developer-friendly
Open where it counts,private where it should be.
Open-source read layer
The REST API and MCP server are Apache 2.0 on GitHub.
14 MCP tools
Sessions, cost, tools, search and a SELECT-only SQL tool.
Read-only by design
OpenWatch reads Claude's data. It never writes to Claude or blocks your people.
Secrets redacted on the device
API keys, private keys, tokens and password values are removed before upload.
Entra sign-in and roles
People see their own activity. Admins see the organisation.
In your cloud account
Attri deploys and runs OpenWatch inside your own cloud subscription.
Questions from engineering leaders
Does it measure developer productivity?
No. It records how Claude is used, not the quality of the work. Treat it as context, not a scorecard.
Is Claude Code in the terminal covered?
The collector reads Claude Code sessions run inside Claude Desktop. Standalone terminal sessions aren't collected by it yet.
Can engineers see their own data?
Yes. Everyone sees their own activity. Admins see the whole organisation.
Can we try it without a deployment?
Yes. Clone the open-source repository, load the sample data and connect Claude Code through MCP in a few minutes.
Someone will ask what happened.Have the answer ready.
Run OpenWatch on sample data in minutes, or have Attri deploy it inside your cloud with live data from your organisation.