Conversations
The Conversations page provides full transcript visibility into multi-turn chat sessions flowing through the platform — whether originated via direct Gateway API calls, the interactive Playground, or team integrations.
Navigate to OBSERVABILITY → Conversations in the Aegis Console to inspect conversation histories and audit dialogue turns.
Filtering & Searching Conversations
- Search Message Content: Search for specific keywords or phrases across conversation messages (press
Enterto search). - Channel Filter: Filter conversations by origin channel:
Gateway (API): Direct API calls from client applications.Playground: Test chats conducted inside the Aegis Console.Teams: Chat interactions from integrated collaboration tools.
- Date Range Picker: Filter sessions by time range (defaults to
Last 24 hours).
Conversations Table Schema
| Column | Description |
|---|---|
| Last activity | Timestamp of the most recent message in the conversation. |
| Channel | Channel badge (gateway, playground, teams). |
| Agent | Monospace Agent ID handling the conversation. |
| User | End-user or identity associated with the session. |
| Turns | Total message turn count. Displays a red Blocked icon if one or more turns were blocked by a Guardrail policy. |
| Tokens | Total token consumption (Prompt + Completion tokens) accumulated across the conversation. |
| Actions | Quick transcript export options. |
Transcript Inspector & Export
Turn-by-Turn Transcript Viewer
Clicking any row in the conversations table opens the Transcript Inspector Modal:
- Displays the complete turn-by-turn dialogue history (User prompts, Assistant responses, Tool executions).
- Clearly highlights turns blocked by Guardrail content safety policies.
- Displays message timestamps, model parameters, and error context.
Exporting Transcripts
In the conversation table or transcript modal, administrators can export session data:
- Download JSON: Downloads the raw conversation transcript payload as a
.jsonfile. - Download CSV: Downloads tabular conversation turn logs as a
.csvfile.