Skip to main content
Coding Agent Insights is in public preview and can change before reaching general availability.
The Coding Agent Insights dashboard shows your team’s coding-agent usage, estimated costs, and trace coverage. The Coding Agent Insights cookbook sets up tracing and a daily Loop automation that identifies recurring problems.

​
Requirements

To show data, the dashboard needs:
  • Coding-agent traces sent by the bt tracing integration for Claude Code, Codex, OpenCode, Pi, Antigravity, or Grok.
  • A dedicated project. The dashboard counts model and tool calls from every trace in the project, including traces logged with a Braintrust SDK, so keep coding-agent traces in a project of their own.

​
Open the dashboard

Go to Dashboards in the project that receives your coding-agent traces, and select Coding agent insights. Coding agent insights is a built-in dashboard, like Cost and quality. It’s read-only, so you can’t add or edit its charts the way you can on a dashboard you create. You can star it like other dashboards. See Browse dashboards. Coding Agent Insights dashboard showing a Usage over time chart of cost, and a table grouped by user. The User column header reads 4 / 12 (33%), and each row lists a teammate's cost, cost change, tokens, sessions, LLM calls, and tool calls.

​
What the dashboard shows

The dashboard answers three kinds of questions about your team’s coding-agent work:
  • Who is sending traces. The dashboard shows which teammates have recorded model calls matching the selected period and filters.
  • How agents are used. The dashboard shows how many sessions, model calls, and tool calls your team’s agents make, and which models and tools they use.
  • Where cost goes. The dashboard breaks down cost by person, model, and branch. For traces sent with an API key or service token instead of an OAuth login, it can also break cost down by key. Users and Keys also show cost changes from the previous period.
Braintrust calculates cost from each model call’s token counts and the model’s pricing. If a span reports its own cost in metrics.estimated_cost, Braintrust uses that instead. A Usage over time chart at the top shows cost across the selected period. To plot token counts instead, click Cost beside the chart and select Tokens. Below the chart, a table summarizes usage for the period. The time range selector in the table toolbar, such as Past 7 days, sets the period for both the chart and the table. Add filter narrows both to a subset of traces.

​
Group the table

The table shows one grouping at a time. To change it, use the grouping selector in the table toolbar, which shows Users by default. Coding Agent Insights dashboard toolbar below the Usage over time chart, with the pointer on the Users grouping selector. Next to it are the Past 7 days time range selector and an Add filter field. Each grouping changes what a row represents and which columns appear:

​
See who is sending traces

In the Users grouping, the User column header shows how many organization members are sending traces, such as 4 / 12. For more detail, click the count to open the User trace coverage display, which lists who is Sending traces and who is Not sending traces. A member counts as sending traces if they have model calls in the selected period that match the current filters. Service accounts aren’t counted.
The dashboard attributes each session to the Braintrust user whose credentials sent it. If teammates share one API key, all of their sessions appear under the key’s owner. To keep per-person usage accurate, have each teammate use their own credentials: their own OAuth login or their own API key.

​
Investigate a row

To see the traces behind a row, click the row. Logs opens, filtered to that row’s user, key, model, tool, or branch, and to the dashboard’s period and filters. To open Logs in a new tab instead, hold Cmd or Ctrl while you click. To ask Loop about a row instead, hover over the row’s name until the Loop icon appears, then click it. Loop opens with a prompt about that user, key, model, tool, or branch.

​
When the dashboard is empty

Until the project has coding-agent traces, the dashboard shows a setup screen instead of data. It includes a command for enabling tracing in your coding agent and a link to the Coding Agent Insights cookbook. The dashboard appears as soon as the first trace arrives.

​
Protect sensitive data

Coding-agent traces can contain source code, file paths, prompts, command output, and any credentials that appear during a session. Braintrust supports two ways to keep sensitive data out of stored traces, and you can use them together:
  • Ingestion redaction (private preview) replaces detected sensitive text before storage. Model-based detection can miss values.
  • Span plugins remove values on each computer before bt sends them, so those values never reach Braintrust. Span plugins require bt v0.21.0 or later.

​
Next steps