Node configuration dialog
Select a node on the canvas and an action bar appears above it. The pencil opens the configuration dialog. It covers the canvas: close it with Esc, with the cross in the header, or by clicking the dimmed background.
Knowledge lookup
RAG Query · rag_query_1
The header carries, left to right: the node family’s colour, its name, a badge with the node type, and the node id.
Renaming
Click the name in the header and it turns into a text field. Enter applies the new name, Esc cancels the edit, an empty string is not saved.
The name is only the caption on the card. Templates address the node by the id shown on
the right of the header: {{ nodes.<id>.output }}. Renaming never changes that id.
Params
The form is built from the node’s schema, so every node type has its own set of fields. Fields sit in two sections with counters: Parameters is open, Advanced is collapsed. Which section a field belongs to is declared by the node itself.
Some fields only appear once a neighbouring field has a particular value: the “Thinking Prompt” of ai_agent, for instance, shows up only when “Enable Thinking” is on.
Model lists come from the workspace: the LLM node, and the embedding and rerank nodes, offer both the platform catalogue and the models of your own connections. Media nodes serve a parameter set that depends on the selected model and is re-fetched when you change it. If the model list fails to load, the dialog says so with a red note instead of showing an empty dropdown.
A field and a connected port
Some fields have a port twin, and then one of the two wins. The editor marks both cases:
| Badge on the field | Meaning | Example |
|---|---|---|
| from port (green) | The value arrives on a connected port; the field is disabled | “Knowledge Base” on rag_query when a base is wired to the kb port |
| overrides the connected port (amber) | The field keeps working and the value arriving on the port is dropped | “Output Expression” on exit over the end port |
Inputs
The Inputs tab has three parts.
Custom Inputs — input ports of your own. A name may contain Latin letters, digits and
underscores, must start with a letter and stay under 50 characters; the names nodes,
inputs, variables, loop, input, run are reserved, and a clash with one of the
node’s built-in ports is rejected too. The value of such an input is read in templates as
{{ inputs.<name> }}. Removing an input also removes the edges that led into it.
Split input ports — a toggle shown on nodes that support splitting (see below).
The port list — every input of the node with its current state.
Inputs (3)
| Port | Wire | id | Connection |
|---|---|---|---|
| Query | ED | query | Entry |
| KB | D | kb | Documentation |
| Embedding | D | embedding | not connected |
Port names come from the node schema and stay English in both locales; only the execution
ports are localized — “Run”, “Success”, “Error”. A port row shows the short wire code
(E, ED, EDS, D, S, L, M, X, Em, Re), the data type, the handle id, the
custom and dynamic markers on user-defined and dynamic ports, a link icon and the name
of the node on the other end. Two collapsible blocks sit underneath: Model — the shape
of the value per the schema, and Value — the value from the last run, if this node
executed.
Outputs
Same layout: a Split output ports toggle and the port list, which holds both execution outputs and data outputs.
Split ports
An ED port carries both the execution signal and the value on a single edge. Splitting
replaces one port with two — <id>_exec and <id>_data. You need it when the trigger
must come from one node and the value from another.
The same toggles are duplicated in the action bar above a selected node on the canvas, next to the “Mirror ports” button that swaps the sides inputs and outputs are drawn on.
Applying changes
Edits reach the canvas immediately, as you type. Apply changes shows “Saved” and closes the dialog; Discard rolls back the last step of the edit history and closes it as well.
Notes
A note node opens a different dialog with no tabs: title, colour, and Markdown content. A note takes no part in execution.