Agents

Agents is the current app surface for deployed-agent operations. In the frontend, the broader analysis area lives under /{org}/analysis/* and defaults to /{org}/analysis/agents.

/{org}/analysis redirects to /{org}/analysis/agents. The sibling analysis subtabs live at /{org}/analysis/charts, /{org}/analysis/data, and /{org}/analysis/notebook. The older /{org}/monitoring route still resolves to the same agents view for compatibility.

Note

Agents is the current app label. Use it after a run, evaluation, or optimization job when you need inspection, query, or telemetry follow-up rather than execution.

What the page is for

Use Agents when you need to:

• inspect live and recent deployed-agent sessions, internal loop events, and report outputs
• move from one deployed session into broader telemetry analysis without leaving the same route family
• query otel_traces and related telemetry tables directly
• export tabular telemetry for external analysis
• open notebook-style analysis that combines runs, spans, evaluations, and summary metrics

The surface is scoped by the current workspace and optional project selector. Those values are carried through the analysis query parameters as you switch subtabs.

Tabs

Agents

The Agents tab is the operational command surface. It is built around deployed session traffic for the current project and gives you:

• a session triage rail for recent production traffic
• an internal event loop view for the selected session
• a report tool output panel that renders saved markdown when the default report tool is used
• transcript-on-demand for the selected session

The page refreshes on a slower operational cadence instead of continuously repainting. Idle sessions stop auto-polling their per-session detail so the view stays readable while you inspect older traffic.

Charts

The Charts tab summarizes recent deployed-agent traffic for the current project:

• a configurable primary chart with Group By and Metric controls
• filters for session status and free-text matching against session ID, agent, title, or model
• session-ID-aware axes when you group by Session ID
• recent internal loop event mix
• report-call volume by session
• a session table under the charts so the current slice remains inspectable as rows

These charts are derived from the recent session and telemetry slice loaded from the sessions endpoint, so they stay operational and relevant to deployed agents instead of acting like a generic warehouse dashboard.

Data

The Data tab is the exact query surface. It provides:

• a SQL editor
• schema browsing for available tables and columns
• partial-query execution from a selection
• CSV export from the result grid

The default example query reads from otel_traces, which is a good clue about the intended use: this tab is for precise telemetry retrieval once you already know the question.

Notebook

The Notebook tab assembles a richer analysis context from:

• runs
• spans
• evaluations
• aggregate metrics

Use it when you need to move from dashboard summaries into exploratory analysis without leaving the app.

Scope and filters

• The analysis routes always start from the current organization URL.
• Workspace and project context come from the current selector and query parameters.
• A project filter narrows the result set, but the underlying telemetry remains workspace-scoped.
• If you need raw trace inspection for one workflow, narrow the run first before widening into the analysis subtabs.

From session to trace to agents

These surfaces are connected, but they answer different questions:

1. start in a session when you need the conversational narrative
2. open traces when you need the exact tool calls and execution spans
3. use Agents when you need pattern-level or exportable telemetry across that work

That means the normal debugging path is:

Question	Best surface
what did the operator and assistant say?	session transcript
which tool call or run behaved badly?	trace browser
is this failure isolated or part of a wider pattern?	Agents Charts
which exact rows do I need to export or query?	Agents Data
how do runs, spans, and evaluations line up together?	Agents Notebook

Investigation loop

1. Narrow the run in the TUI

Use the session browser or trace browser first when the problem starts from one conversation. That gives you the runtime and project context before you move into wider analysis.

2. Carry the same workspace and project into Agents

The analysis routes preserve workspace and project through query parameters and the project selector. Keep those aligned with the TUI context so you do not accidentally compare the wrong workload.

3. Choose the right subtab

• use Agents for deployed session traffic, report review, and event-loop inspection
• use Charts for trend-level questions about agent traffic shape, alert pressure, event mix, or model footprint
• use Data for exact SQL retrieval and CSV export
• use Notebook when you need runs, spans, evaluations, and summary metrics together

4. Export the right artifact

• export a session transcript when you need narrative evidence
• export CSV from the Data tab when you need structured telemetry rows
• use the Notebook when you need richer in-app analysis before exporting elsewhere

What agents should assume

• Agents is the current app entry point for deployed-session operations.
• The Charts tab is the fastest summary for recent deployed-agent traffic.
• The Data tab is the right surface for precise row-level retrieval.
• The current workspace and project selectors materially change the result set.
• Notebook data is assembled from multiple stores, so it is an analysis workspace rather than one canonical API object.
• Session text and telemetry are related but not interchangeable; agents should not treat a transcript export as trace data.

For adjacent surfaces, use Sessions & Traces for narrative-first inspection, Tracing for span production and exporters, Projects for grouping semantics, Evaluations for job context, and Security Evaluation Operations for an end-to-end operator path.