conversationsevaluationsagents
Conversation traces, MCP tools in fixtures, and a tighter chat layout
See every tool call behind an answer and export the transcript, test agents that use connected apps, and read more of a conversation without scrolling.
Added
- Conversation trace — a Trace tab on any conversation shows the full turn-by-turn record behind an answer: every tool the agent called, the arguments it sent, the result it got back, and the model and token counts per turn. Export writes the whole thing to Markdown for sharing or JSON for tooling. Available to workspace owners and admins, and each view is recorded in the security audit log. See diagnosing an answer.
- Connected-app tools in fixtures — the fixture tool picker now lists the MCP tools an agent's connected apps expose (Google Calendar, DocuWare, and so on) next to the built-in ones, with the provider's own argument names filled in. See fixtures.
Improved
- Author a fixture straight from a failed run. A blocked badge in a run's trace is now clickable: it opens the fixture editor already filled in with that tool and the exact arguments the agent tried to use, so fixing a case is a two-click round trip instead of retyping the call. See fixtures.
- Every dropdown now uses the app's own menu, so it follows your theme instead of the operating system's, stays aligned with the field it belongs to, and can show a short description under each choice. This also fixes menus that opened behind a panel or ran off the bottom of the screen.
- Denser chat. Dashboard chat, Live Sessions and the conversation drawer now share one spacing scale, and the web widget is tighter throughout — noticeably more conversation visible before you have to scroll, on every screen size.
- The widget preview page works on a narrow screen. The backdrop and draft/published switches moved out of the mock browser's address bar into a row that wraps, the agent list and config panels collapse into overlays sooner so the preview itself is never squeezed, and the floating widget now mounts inside the page area rather than over the browser chrome.
Fixed
- Password reset requests are now limited per email address and per network address, and require the anti-automation check the form already displayed. The form can no longer be used to send repeated mail to somebody else's address. Resetting your own password is unchanged.
- A malformed request to the password reset endpoint returned a server error instead of a validation message.