Switching mode
Toggling Conversation mode on or off is destructive: the two modes use incompatible Start and End nodes, so switching deletes the current Start Point inputs and the current Final node configuration.
You can only toggle the mode on a Draft version. Published versions are read-only.
What gets deleted
| You toggle to… | What's deleted |
|---|---|
| Conversation mode ON | Typed Start Point inputs (Text, Number, File URL, Options, JSON, etc.) and the Outputs node's keys. |
| Conversation mode OFF | Seeded Chat History and the Final Output template. |
What's preserved
Everything else stays:
- Every other node on the canvas — LLM, KB Search, API, Python, etc.
- All wiring between intermediate nodes.
- Every Custom Attribute — secrets, per-project env values, etc.
- Every environment variable — these live at the project level and are shared across Tools, Agents, and KBs.
- Other configuration: guardrails, execution rules per node, limits, integrations bound to the resource, version history of published versions.
A node that references a now-deleted Start Point variable will show the standard "undefined variable" indicator. Fix these manually after the switch.
The confirmation modal
When you flip the toggle, a confirmation modal opens before the change is applied. It states, in plain language:
- What conversation mode is and how it differs from the default.
- That switching deletes the current Start Point inputs and Final node configuration.
- That environment variables and Custom Attributes are preserved.
- That this action applies to the current Draft only and does not affect any Published version.
The modal has two actions:
- Cancel (default) — leaves the toggle as it was.
- Switch mode (destructive style) — applies the change.
There is no "Don't show again" option — the warning fires every time you switch a Draft.
After the switch
- The Start Point drawer now shows the new mode's input type (Chat History panel for conversation mode; Inputs tab for task mode).
- The final node on the canvas switches to the new mode's variant (Final Output for conversation; Outputs for task).
- All preserved nodes appear unchanged.
- Any node that references a deleted Start Point variable shows the "undefined variable" indicator — manually rewire to a still-valid variable, or remove the reference.
No auto-mapping
The platform does not try to auto-map typed inputs ↔ chat history when you switch — that mapping is impractical given how different the two surfaces are. Explicit deletion keeps the model simple.
Switching as part of migration from AI Chains
Tools migrated from the legacy AI Chains primitive are created with Conversation mode on by default. If you want to convert one to a task-mode Tool, you can — fire the destructive warning, accept it, and rebuild the Start Point inputs and Outputs keys. See Migration from AI Chains.