Observability
Per-team traces of what your Teammates do: model calls, tool calls, token usage, and who asked for it.
Every action your Teammates take is traced, so you can see what happened during a run without reconstructing it from chat logs after the fact.
An isolated workspace per team
Your account gets its own observability workspace, isolated from every other customer's — your traces are never pooled with anyone else's. You launch into it directly from the dashboard; there's no separate account to set up or credentials to manage.
What a trace shows
A trace covers the mechanics of a Teammate's turn: which model was called, which tools it invoked, how many tokens it used, the session it belongs to, and which team member's message triggered it.
Note: Traces capture activity metadata, not the content of prompts or responses.
Cost attribution
Because token usage is recorded per call, traces let you see where usage is concentrated — which Teammate, which session, which model — alongside your account balance and usage figures in the dashboard. Traces are the activity detail; billing itself is handled on the Team & billing page.
Who can access it
Observability is managed the same way billing is: team owners and admins control access to your observability workspace. Other members don't get a direct line into it unless an owner or admin sets that up.
Asking a Teammate about itself
Because a Teammate can query its own recent activity, you can ask it directly — "what did you do in the last hour?" — and it'll pull from its own trace history to answer. This conversational access is available to the same owner/admin roles that manage observability more broadly.
API and MCP
See API & MCP for how tokens and scopes work across the platform; observability access itself is managed from the dashboard.