Flows: Multi-Agent Templates in One Click
Drop a complete, pre-wired set of agents onto your canvas in one click — peer review, pipeline, or watcher — and save your own setups as reusable templates.
Wiring two agents together for a review loop or a pipeline is the same handful of steps every time: spawn a tile, spawn a second tile, draw a connection, configure the trigger, configure the transform, set loop protection. Flows collapse all of that into a single action. Pick a template, type your task, and a connected set of agent tiles appears on the canvas, ready to run.
What you can do now
- Drop a ready-made multi-agent setup in one click — three built-in Flows cover the most common patterns, no manual wiring required.
- Start with your task up front — every Flow opens a kickoff dialog that asks for the prompt first, so the entry agent receives it the moment it's ready instead of landing on two empty terminals.
- Save your own canvas as a Flow — turn any arrangement of agent tiles and connections into a reusable template you can drop again later.
- Re-drop a Flow onto an existing instance to refresh it in place — instead of duplicating tiles, the live instance updates.
How to try it
- Open the collapsible Flows panel on the canvas's left edge.
- Click a built-in Flow (Peer review, Pipeline, or Watcher).
- Type your task in the kickoff dialog and press Cmd+Enter (or click "Start with task").
- The agent tiles appear on the canvas, wired together, with your prompt sent to the entry agent automatically.
The three built-in Flows
| Flow | What it does | Stops when |
|---|---|---|
| Peer review | One agent drafts, another reviews each turn and replies with feedback | The reviewer says LGTM |
| Pipeline | The first agent's full output is handed to the second once it finishes | After one handoff |
| Watcher | A second agent stays on standby and only reacts when the source agent's output mentions a keyword like error, warn, fail, done, or review | After several rounds |
Dropping a built-in produces exactly what you'd get by spawning two tiles and drawing one connection with those settings yourself — Flows just remove the manual assembly.
Why it matters / use case
If you keep building the same review loop — Claude drafts, Codex reviews, you read the feedback — saving it as a Flow means next time is one click plus a prompt. For teams that gravitate toward a particular pipeline shape, Flows turn a recurring setup chore into a template everyone can reuse. And if none of the built-ins fit, you can still wire tiles by hand or ask MadoAgent to orchestrate something custom.
Related docs
What's next / limitations
Flows capture tiles running Claude Code, Codex, Amp, or OpenCode — a bare shell tile is skipped, and saving a canvas with no recognized agent tiles is rejected with a toast. Saved Flows are stored locally on your machine and reload with the rest of your canvas state.