Kernlift

Chat conversations

Read the conversations your users had with an agent: who, which agent, in which language, and every message part.

Every chat a user has is stored as a conversation with its messages. /admin/chats is the read-only view of them, paginated, and /admin/chats/$conversationId is one thread with each message's role and parts. Operators use these pages to check what an agent said to a customer.

Before you begin

  • ai.read, the same key that opens the AI operations pages. Conversations are AI output, so the operators who watch AI tasks also review conversations. See Roles and permissions.
  • At least one conversation. Chat needs a model channel: see AI providers if /app/ai reports nothing configured.

Set it up

Give the reviewer ai.read

It is a read key. /admin/chats has no write path. You cannot edit a conversation, delete it or reply as the assistant.

Read the list

/admin/chats pages through conversations, newest first, showing the account, the agent key, the language and when it was last updated. Page size is a search parameter, so a shared link opens the same page for someone else.

Open one thread

/admin/chats/$conversationId renders the messages in order with their roles: system, user, assistant, tool. Tool messages are shown, so you can see which tool call produced an answer.

What a conversation holds

Prop

Type

Messages are persisted as they stream. An interrupted response remains in the conversation with its received content and message status.

Verify

  1. Hold a short chat from /app/ai, then open /admin/chats. The conversation is at the top with your account and agent key.
  2. Open it. The system prompt, your messages and the assistant's replies are in order.
  3. Change pageSize in the URL. The list uses that page size, and the link works in another browser.
  4. Sign in with a role that lacks ai.read. The page denies access.

Reference

Next steps