Surfaces
The largest group: canvases, editors, terminals, maps and charts — the components a user actually looks at and an agent actually drives.
0/3 lessons
0%
fancy-flow: an engine, and an editor you can leave behind
~9 min
fancy-flow is a headless workflow engine with an optional React Flow editor. The engine lives at /engine and imports zero React — you can run workflows on a server with no DOM anywhere in sight.
On AI it is a shuttle, not an engine. Core declares a registerLlmClient contract and never imports a provider SDK. Adapters are opt-in, on the ./llm/vercel-ai and ./llm/prism subpaths. The discipline this buys: adding a new model provider never touches core, and core never drags a vendor SDK into the bundle of an app that does not use AI at all.
It has a PHP runtime twin, fancy-flow-php, that runs the same WorkflowSchema JSON and must produce the same outputs. That parity is enforced by golden fixtures, not by intent.