Chat
Chat is the workbench for talking to a workflow. Every message you send starts one run: the text arrives at the entry node, and the reply is collected from exit and printed into the conversation as it is generated.
Picking a workflow
The top bar holds a dropdown with the workspace’s workflows. Deployed ones show their version number next to the name; the rest are marked as not deployed.
Chat only runs the deployed version. Until a workflow is published, the conversation is replaced by the warning “This workflow has not been deployed yet” and a Deploy workflow button; the Manage deploy link on the right opens the deploy tab of the editor.
Sessions
A session is a separate thread of conversation: its own message history and its own turn queue. The plus button in the CHATS list creates a new session with a random id; clicking a row switches to it.
The selected workflow and session are part of the page address
(?workflow=…&session=…), so a link to one specific conversation can be bookmarked or
sent to a colleague.
The list shows every session of that workflow, not only the ones started here: the public chat page, the widget and Telegram all write into the same message store. Up to 50 sessions are loaded, most recently active first.
Chat
CHATS
sessions of this workflow
| Session | First message | Messages |
|---|---|---|
| New chat | How much is delivery to Kazan? | 6 |
| tg:214… | /start | 24 |
| 9f31c2… | I need an invoice | 3 |
Chat
deployed version v3
Sending and stopping a reply
- Type a message and press Enter (Shift+Enter inserts a line break).
- While the workflow is working, a “Running workflow” marker sits under the conversation and the reply is printed as it is generated.
- The red square button stops the current turn. The queue survives it — the next message of the session starts on its own.
Messages of one session run strictly in order. Send a second one before the reply arrives and it joins the queue, with the panel showing how many turns are waiting. Queue depth is capped by the plan: a message over the limit is rejected and a “Failed to send” line appears above the composer.
Rendering comes from the live session channel rather than from the response to your send. That is why the same session opened in two windows shows the same stream, and why a turn arriving from Telegram or the widget is visible here live as well. If the connection drops, the panel shows “Reconnecting…” and resumes where it stopped.
Hover your own message to get the Rerun from this message action: it deletes that message and everything after it, and puts the text back into the composer.
Attachments
The paperclip button attaches one or more files. A file is first uploaded into the workspace store (it shows up in the Files section) and the message carries a reference to it, so the workflow receives the file together with the text of the turn. A file picked by mistake is removed with the cross on its chip before sending.
Clearing history
The trash icon in the panel header deletes all messages of the current session. It is irreversible and touches the conversation only: the state of memory nodes is not reset.