How threads are built
A thread is constructed from events with namechat. The SDK groups consecutive chat events that share the same thread_id (or, when none is supplied, the same agent and user within a time window).
chat event becomes one ThreadMessage. The aggregate Thread record carries:
started_at,ended_at,message_count- Total tokens and total cost across the thread
- Last message preview for the thread list
What you see per thread
Drilling into a thread
Click any thread row to open the full conversation. Each message exposes:- The full
content - Per-message latency
- The associated run, with a link out to the trace
- Any user feedback attached via the feedback API
Filtering
Common workflows
Find every conversation a user had with one agent
Find every conversation a user had with one agent
Filter by Agent and User. Threads list returns the matching conversations chronologically.
Audit a conversation that received negative feedback
Audit a conversation that received negative feedback
Toggle With feedback and sort by Last activity descending. Open each thread and inspect the feedback annotation per message.
See the trace behind a single message
See the trace behind a single message
Open the thread, click the Run link next to the message you care about — that opens the trace detail for the underlying run.
Related resources
Traces
Underlying chain-of-calls per message.
Event reporting
How
chat events are emitted.
