Conversation list
The list supports:- Search — the “Search conversations…” box filters the list.
- Filters — environment (Production / Development / Staging) and use case.
- Time range — All time, Last 24 hours, or Last 30 days.
- Sort — Newest first, Oldest first, Most messages, Fewest messages.
- Pagination — page sizes 10 / 25 / 50 / 100 with Previous / Next; the total count loads separately.
Columns
The Columns button shows or hides columns; column widths can be dragged. Preferences are saved in your browser.
Clicking a row opens the conversation detail in a new tab.
Conversation detail
The header shows the conversation ID, date, duration, and turn count, plus badges when they apply: a frustration score (shown when the score is 5 or higher), the tool-failure count, and the use case with its confidence. Previous / next links step through neighboring conversations. A toggle switches between the two views: Full Trace and World State. While a conversation is still mostly unprocessed, a strip lists the pending pipeline stages (segmentation, world-state, cluster, frustration); it disappears once most stages have completed.
Full Trace
Full Trace is the raw timeline: every message and content block in order. Each row shows content appropriate to its type:- User messages — the message content, rendered as markdown.
- Agent responses — the model and provider above the response text.
- Thinking — collapsed to a single expandable line.
- Tool calls — expandable input and result; failed calls are highlighted.
- Tool Call Failure — the tool name and error, with Jump to failure.
- User Frustration Detected — the score, trajectory, and primary cause, with clickable quotes that jump to the quoted turn.
World State
World State shows what Moda extracted from the conversation: the tasks the user pursued and the facts established along the way. It has two tabs. Tasks lists the conversation’s task threads with a resizable detail pane. Each thread has a status (Open / Resolved / Cancelled) and can contain subtasks (Open / Done / Blocked / Cancelled). The detail pane shows a progression timeline of actions — Message, Tool call, Correction, Subtask opened, Subtask completed, Failure, Retry — and each step can jump back to the matching turn in Full Trace. Add to eval set saves a task as a replay case for Replays and Playground. Facts lists the facts extracted from the conversation; when the position is known, each fact is tagged with the turn where it was established. Both tabs are searchable (“Search threads” / “Search facts”); Tasks additionally supports filtering by thread status, subtask status, and action type, and sorting by Most recent turn, Status, or Title (A→Z). While the build is in progress, a “Still building world state” banner shows partial results and updates live.User memory panel
At the top of the World State view, a collapsible User memory panel shows a persona document built from the user’s messages — voice, decision style, and constraints — used to simulate this user in replays. The panel header shows how many user messages have been folded in, and each observed trait carries a chip with its occurrence count and the last message where it appeared.Trace viewer
A standalone trace viewer exists athttps://moda.dev/trace/<traceId>. It renders a span tree for one trace with a span detail pane, and supports a ?span= parameter to deep-link a specific span. It is auth-gated and not linked from the sidebar — open it by URL when you have a trace ID.
Next steps
- Signals — the detections that produce the banners and badges on conversation pages.
- Use Cases — the clusters behind the Use case column.
- Replays and Playground — where tasks added to an eval set are run.
- Data API: conversations — fetch conversations and world state programmatically.