Clients

Clients answers the question “what have people already written to this workflow”. It is a viewer: sessions on the left, the full conversation of the selected session on the right.

Picking a workflow

The selector in the top bar lists the workspace’s workflows, with the version number next to deployed ones. Until a workflow is picked, the page shows the “Select a workflow” prompt.

The selected workflow is part of the page address (?workflow=…), so the link can be saved.

The session list

Sessions are ordered by the time of the last message, newest first, and up to 50 are loaded. Each row shows a shortened session id, the relative time of the last message, the first user message and a message counter.

Every channel writes into the same store, so conversations from the Chat section, the public chat page, the widget and Telegram all appear here. The shape of the id is the easiest way to tell them apart:

• tg:<chat id> — Telegram; forum topics add :<topic id>;
• a random UUID — the public chat page or the embedded widget (each visitor gets one);
• chat and other names created in the Chat section.

The conversation

Clicking a session opens its conversation, rendered the same way as in chat: user turns, workflow replies, and — for reasoning models — an expandable Thinking block. Up to 200 messages are shown, counted from the start of the conversation; the session id is printed above the first message.

An empty list means no message has been stored for this workflow yet: check that the channel is actually connected and the workflow is deployed.

Where to go next