Langflow already thinks in nodes and edges — the move is shorter than it looks, and the canvas on the other side stays live while a run executes.
There's no Langflow file importer — our importer covers Flowise exports only, and we'd rather say that than half-convert your flow. The honest path is generate, not import:
| Langflow | LiveGraph |
|---|---|
| Agent component + tools | Worker node — role, prompt, and model per node, with its tools scoped per node |
| Prompt / Model components | The node's prompt and model picker — any provider per node, keys stay yours |
| Conditional / routing components | explicit edges, or auto edges where a router picks the next specialist |
| Chat Input / Output + Playground | Runs start from chat, the canvas, schedules, or webhooks — not a hosted chat surface |
| Tool and MCP components | Per-node MCP servers with an exact-name tool allowlist, http_request, or file access |
| Vector store / RAG components | No built-in vector store — wire retrieval in through an MCP server or HTTP endpoint you control |
code doesn't execute on the canvas — rewire the same capability as an MCP server or HTTP endpoint the node can call.In Langflow you test a flow in the Playground and read the log when it finishes — the canvas is a build surface, not a live one. On LiveGraph the run executes on the same canvas you built: you watch each hop as it happens, a run parks at an approval gate until a person says yes, and dragging an edge mid-run steers the run you're watching instead of restarting it. Generated graphs and hand-built ones get the same treatment — nothing lands in a black box.
Create an account, paste your simplest flow's export into the describe box, and run it once — or watch the live demo first: a real multi-agent graph running in your browser, no signup.