Observability

Three screens cover what happened: Sessions, Session Trace, and Flows. Token spend lives on the TokenOps dashboard. Session Trace and Flow Detail show much the same data from two angles.

​

Sessions

Your past conversations, from Orchestrator or direct Chat. Each row shows:

• The agent’s name and initial avatar, or Orchestrator if no single agent handled it
• A message count and a preview of the last message
• Time since last active, grouped under Today, Yesterday, This Week, Older

Search filters by agent name or message text. New Chat starts fresh; the trash icon removes a session. Clicking a session reopens the thread in Chat. A finished assistant reply carries a trace icon next to Copy — that opens its full trace.

​

Session trace

Every span behind a single query, in order, including nested agent-to-agent calls. The stats row shows Spans, Duration, Tokens (input + output), Cost when available, and the Session ID. The span list is indented to show nesting. Each span shows its name, model for LLM calls, token count, and duration; a red dot marks an error. Click a span for its kind, span ID, status, start and end times, model, and input/output token split.

​

Flows

Every multi-agent interaction, as a searchable sortable table: Search filters by agent name or query text.

​

Flow detail

Summary cards for Status, Root Agent, Duration, Started, Steps, and Query, then a Trace timeline. Each step shows:

• A status badge
• The agent it called, with a preview of what was sent (hover for the full text)
• A bar sized and positioned to show when it ran relative to the whole flow — the slow hop is visible at a glance
• Its duration

​

Tokens and cost

Token spend has its own screen — see TokenOps for per-agent cost, operations, agent hours, and latency by month, with CSV export. Cost also appears inline: a session trace’s stats row shows that query’s token count and dollar cost, so you can attribute one expensive answer without leaving the trace.

​

API

Everything these screens show is available under /api/observability/*:

​

Configuration

Agents are traced with no code changes — every deployment gets OpenTelemetry configuration injected into its spec, so instrumentation starts at boot and traceparent propagates across agent-to-agent hops automatically. If you run your own control plane, these are the knobs:

​

Related