Conversations
Conversations lists every agent conversation in the workspace, across all channels.
Finding a conversation
Section titled “Finding a conversation”Filter by channel, agent or date range, or search. The search looks inside the messages themselves, not only the participant and the title. Filters live in the URL, so you can share a filtered view as a link. The list shows every conversation by default; tick Active only to show only live ones.
Reading a conversation
Section titled “Reading a conversation”Open a row to see the transcript, rendered the way the chat renders it (tables, lists, code). Next to it is the agent’s worklog: the tools it called, the sub-agents it delegated to, and the files it produced.
All channels are listed: web chat, WhatsApp, Google Chat, Telegram, Slack, A2A, OpenCode and the internal agent playground. Voice records audio rather than turns, so it shows the session metadata and the recording.
Sensitive data
Section titled “Sensitive data”Credit card numbers, API keys, private keys, passwords and bank accounts are detected as messages are stored. The conversation gets a badge for the most sensitive item found, the values appear masked (••••1111), and a panel lists what was found by category.
Revealing a value requires the conversations.pii_reveal permission. You reveal one category at a time, and each reveal is written to the audit log with your user and the time. There is no mode that leaves values unmasked.
Phone numbers, email addresses, ID numbers and IP addresses can also be detected but are off by default; a workspace admin can turn them on. Rule changes apply to new messages; use Re-scan on a conversation to apply them to messages stored earlier.
Exporting
Section titled “Exporting”With conversations.manage you can export the filtered list as CSV, or a single conversation as Markdown or JSON. Exports are masked the same way as the screen, and every export is written to the audit log.
Retention
Section titled “Retention”The conversation record shown in this hub is kept for one year by default. A workspace admin can change this with the conversations.retention_days setting, and can also run the cleanup on demand. See Security overview for how long other kinds of data are kept.
Access log
Section titled “Access log”Access log, in the Monitor section, shows every time someone opened a transcript, revealed a value or exported a conversation: who, when, and for a reveal, which category. It requires conversations.audit.
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
conversations.view |
Listing conversations |
conversations.audit |
Reading other people’s transcripts and the access log |
conversations.pii_reveal |
Revealing masked values |
conversations.manage |
Exporting |
The workspace admin role has all four. See Users and roles.
