Estimated spend per day, by model
People
Click a person to see only them.
Tags
From CC_* variables in Claude Code's settings. Click one to see only its usage.
Models
Where the spend goes
Your conversation, subagents, and Claude Code's small background calls.
Tools
Billed and estimated
Billed is AWS's bill, by the IAM Identity Center user who made each call: exact, a day or so behind, and not per tag. Estimated is Claude Code's own figure at list price, current to within about five minutes. Billed with nothing estimated means telemetry isn't arriving.
Sessions
The 200 most recent in the range. Click one for its prompts, model calls and tools.
Session
Models, and where they run
The Anthropic models Bedrock offers in this region. Bedrock refuses the ones you turn off, for everyone and
from any client, within a minute of saving. The allowed ones are what Claude Code's
/model offers people who install from here, starting on the default. Claude Code also makes
small background calls (a session's title, say) with config.yaml's haiku model; with that one off, they fail
quietly and sessions carry on.
Required tags
Tags every Claude Code session should carry, from CC_ variables: project is
CC_PROJECT. Claude Code asks at the start of each session, so a change applies to new sessions
straight away, with nothing to install again. Warn tells people what's missing; require
also holds their prompts back until it's set.
Budgets
In USD, per person. Whoever reaches one can't call Bedrock until the period ends (UTC; weeks start on Monday), you raise it, or you reset them. Spend is the larger of the estimate and the bill. An empty field means no limit for everyone, and the default for a person; 0 blocks someone outright.
This period
Use Claude Code with your company account
- Run it in a terminal. It installs Claude Code and the AWS CLI if you don't have them, and signs you in with your company account in the browser, once.
- Start
claude. When your sign-in expires, Claude Code opens the sign-in page again.
Tagging your usage
Any CC_ variable in a Claude Code settings file's env becomes a tag on your usage,
to filter and group by here. Put them in a repository's .claude/settings.json (for everyone
working in it) or .claude/settings.local.json (just you):
{ "env": { "CC_PROJECT": "apollo", "CC_TEAM": "payments" } }
For one session, put it on the command line: CC_PROJECT=apollo claude. In a repository that
sets its own, the repository's wins, so override it with
claude --settings '{"env": {"CC_PROJECT": "apollo"}}'. Without any, your usage has no tags.
Models
/model in Claude Code lists the models your admins allow, and new sessions start on their
default. What you pick in /model stays your choice. When the admins change the list, download
and run the installer again to see the new one.
What it changes
Claude Code and the AWS CLI in ~/.local if you don't have them, two sections in
~/.aws/config, the Bedrock, model, telemetry and tag-check settings in
~/.claude/settings.json (the rest of that file stays as it is), and a small helper in
~/.claude/cc-bedrock/. Telemetry is counts, costs, models and tool names: never your prompts,
Claude's answers or your code.
The same settings for /Library/Application Support/ClaudeCode/managed-settings.json (or
/etc/claude-code/ on Linux); see the README.