Conversations Workflow

The Conversations page is the dashboard view for session-level history.

Use /dashboard/dev/conversations when you want to inspect one conversation or run in detail rather than reasoning from API responses alone.

What you can do on this page

• select a project
• search conversations by title or session id
• create a new conversation record
• open a conversation detail view
• inspect message count and recency
• delete a conversation when needed

When this page is useful

This page is most valuable when you are debugging:

• session-scoped retrieval behavior
• whether a conversation was created under the right project
• whether the session id in your app matches what RetainDB stored
• why a user’s latest interaction is not showing up where you expect

Recommended workflow

1. Select the project first.
2. Search by the session id your application actually used.
3. Open the matching conversation.
4. Check title, message count, and timestamps.
5. Compare that against the session-scoped memory or retrieval behavior you are debugging.

What this page is not for

This is not the best page for durable user memory. If you are trying to inspect long-lived facts or preferences, use the Memories page instead.

Conversation history answers “what happened in this run?” not “what does RetainDB know long-term about this user?”

Common mistakes

Looking for a user profile here

If the behavior spans multiple sessions, the Conversations page is too narrow.

Using the wrong project

The project selector matters. An empty list often means the session exists somewhere else, not that it never existed.

Treating title search as identity search

For reliable debugging, search by session_id whenever possible.

What a healthy result looks like

• the conversation appears under the expected project
• timestamps roughly match the real app timeline
• message count is plausible for the run you are inspecting
• the detail view gives you enough context to compare with memory extraction or retrieval results

Next step

If you need to inspect the memory that came out of those interactions, go to memories workflow. If you want the API surface for session inspection, read profiles, sessions, and jobs.