<!-- Full-page Markdown export (rendered HTML → GFM). Source: https://neotoma.io/ar/inspector/conversations Generated: 2026-04-27T12:48:36.993Z --> # Inspector, Conversations & turns Conversations and turns reconstruct the chat history Neotoma has captured. Every turn is stored as a `conversation_message` entity (alias `agent_message`) with role, sender kind, content, attachments, and a stable `turn_key`; the parent `conversation` entity glues them together with a topic title and participant kind. Inspector renders these rows back into a familiar transcript-style view, then layers the underlying graph on top, so you can see not just *what was said*, but every entity each turn produced or cited, and the agent that wrote it. ## Conversation list The list view groups all `conversation` entities with their turn count, last activity, primary participants, and `thread_kind` (`human_agent`, `agent_agent`, `multi_party`). It supports filters by thread kind, agent identity, and time range, and deep-links into individual turns. inspector.neotoma.io/conversations Inspector Neotoma Dashboard Conversations Turns Compliance Activity Feedback Entities Observations Sources Relationships Graph Explorer Schemas Timeline Interpretations Agents Agent grants Settings Conversations 312 threads · 8,240 turns human\_agent (260)agent\_agent (38)multi\_party (14) | Title | Thread kind | Turns | Agents | Last activity | | --- | --- | --- | --- | --- | | Q2 budget review | human\_agent | 24 | claude-code | 12:41 | | Vercel migration plan | human\_agent | 18 | cursor-agent | 11:08 | | Receipt triage (April) | human\_agent | 9 | ingest-pipeline | 10:55 | | Planner ↔ Executor sync | agent\_agent | 42 | planner, executor | Apr 26 | | Customer interview · Sarah P. | multi\_party | 31 | user, claude-code, gpt-5.5 | Apr 24 | Per-conversation summary: title, turn count, last activity, primary agents, and thread kind. ◆ ## Conversation transcript Open a conversation and Inspector reconstructs the transcript by ordering its `conversation_message` children by `turn_key`. Each turn shows role (`user` / `assistant` / `agent` / `system` / `tool`), `sender_kind`, the verbatim `content`, attached files via `EMBEDS`, and the entities the turn `REFERS_TO`. inspector.neotoma.io/conversations/conv\_3a2 Inspector Neotoma Dashboard Conversations Turns Compliance Activity Feedback Entities Observations Sources Relationships Graph Explorer Schemas Timeline Interpretations Agents Agent grants Settings Q2 budget review conversation · 24 turns · human\_agent claude-code · swapr 24 → apr 27 useroperator12:30 What did we spend on subscriptions this quarter? REFERS\_TO · transaction (3) assistantclaude-code12:30 Top categories: Vercel ($420), Linear ($96), Notion ($60). I cited 124 transactions. REFERS\_TO · report · Q2 spend patternREFERS\_TO · transaction (124) useroperatorEMBEDS · 111:08 Here's the Vercel invoice, confirm the period. REFERS\_TO · receipt · vercel-2026-04 assistantclaude-code11:08 Period 2026-04-01 → 2026-04-30. Stored as receipt; matched to transaction tx\_4b1. REFERS\_TO · transaction · tx\_4b1 Per-turn transcript with role, agent, content, embedded files, and the entities each turn referred to. ◆ ## Sender kind and agent-to-agent Every `conversation_message` carries `sender_kind` alongside the legacy `role` field. For agent-to-agent traffic the sender is `agent` with a stable `sender_agent_id` (and optional `recipient_agent_id`) so multi-agent chains can be reconstructed exactly. The transcript view colour-codes turns by sender kind and surfaces the agent identifier inline. ◆ ## Embedded files and references Files attached to a turn (PDFs, screenshots, CSVs) become `file_asset` entities linked to the message via `EMBEDS`. Inspector renders an inline preview where it can and a "View source" link via `GET /sources/:id/content` when it can't. Entities each turn cited or produced are listed inline as `REFERS_TO` chips, each clickable to the entity detail. ◆ ## Compliance view The Compliance tab on a conversation re-renders the same turns with per-row trust tier, signing key thumbprint, and "did the assistant store its reply?" indicators, so you can audit whether agents are following the per-turn persistence contract described in the [agent instructions](/agent-instructions). Missing assistant turns or anonymous-tier writes show up in red. inspector.neotoma.io/conversations/conv\_3a2/compliance Inspector Neotoma Dashboard Conversations Turns Compliance Activity Feedback Entities Observations Sources Relationships Graph Explorer Schemas Timeline Interpretations Agents Agent grants Settings Compliance · Q2 budget review 24 turns · 0 anonymous · 2 missing assistant stores 22 / 24 ok2 missing | Turn | Role | Tier | Signed by | Reply stored | | --- | --- | --- | --- | --- | | #4 | user | info | operator (sw) | ok | | #4 | assistant | software | claude-code (sw · ed25519) | ok | | #5 | user | info | operator (sw) | ok | | #5 | assistant | software | claude-code (sw · ed25519) | missing | Per-turn compliance view: trust tier, signed-by, and whether the agent persisted its reply.