The AI assistant in the editor
The assistant builds and edits the graph for you: you describe the task in words, it proposes a set of changes, you apply or discard them. The Workflow Assistant panel is open on the right by default; the bot button on the right of the toolbar collapses and expands it. Drag its left edge to resize; on narrow screens it becomes an overlay drawer.
Customer support
Workflow Assistant
Describe what to build…
How to phrase a task
Write what you would tell a colleague: which node you need, where it should be wired, what the output should look like. Enter sends the message, Shift+Enter inserts a newline.
Along with your text the assistant receives:
- the current canvas graph — unsaved edits included;
- the selected nodes, so “fix this node” resolves to concrete ids when you selected it on the canvas beforehand;
- the last few messages of this conversation;
- a sample of the input data — the entry envelope of a recent run, so the assistant uses real field names instead of guessing them.
What you see while it works
The turn streams, and blocks of several kinds appear in the conversation:
- reasoning — italics with a rail on the left;
- actions — monospace rows with a tick or a cross: these are its tool calls (add a node, change a config, look up a node type, read a past run);
- auto-repair — an amber block listing what was fixed mechanically;
- error — a red block with a Retry button.
While the turn runs, the dot next to the panel title pulses and the send button is replaced by Stop. The bin icon next to the checkbox clears the conversation.
Auto-repair and validation
After every round the assistant validates its working graph against the strict rule set — the same one that gates deployment. Some findings have a single mechanical fix; those the assistant applies itself and reports in an Auto-repair block instead of spending a round on them.
It also has its own debug run: it can execute the graph on the real engine with external and paid nodes stubbed out, to check its own work. That run is not billed and is allowed at most three times per request.
The change preview
When the assistant proposes an edit, a Proposed changes block appears above the input box — a line-by-line list.
Customer support
Proposed changes
| Change |
|---|
| + Node: AI Agent (ai_agent) |
| + Node: Buffer Memory (buffer_memory) |
| ~ ai_agent_1: system_prompt=You are a support assistant…, max_iterations=8 |
| + Edge: buffer_memory_1[memory_out] → ai_agent_1[memory] |
| − Edge: e_llm_1_exit_1 |
Lines that belong to a concrete node are clickable: the click focuses the camera on it. For a config change the fields and their new values are listed, not just the fact that something changed.
Apply moves the changes onto the canvas. Discard throws the proposal away and leaves the graph as it was.
When the assistant builds a graph almost from scratch (the canvas held only an entry and an exit), a single auto-layout pass runs after the apply — otherwise the new nodes would land in a pile.
Auto mode
The Auto checkbox (“Auto-apply changes without confirmation”) removes the confirmation step: every proposal goes straight onto the canvas and you watch the graph assemble as the answer streams. The setting is remembered in the browser.
The mode is convenient while building a new workflow from scratch, where you are going to review the result as a whole anyway. For edits to a working graph leave it off, so every change passes through your review.
Test runs from the panel
Two buttons in the panel header run the workflow without leaving the conversation:
- Mock run — executes the graph with external and paid nodes stubbed out.
- Test run — a real run; it asks for confirmation, because it may send messages, call paid models and spend credits.
Both are disabled while there are unsaved edits: the run executes the saved version, so otherwise you would be testing a graph other than the one you see. The run id lands in the conversation — you can then ask the assistant to look into that run, since it has tools for reading runs and the inputs and outputs of individual nodes.