1.0 · Canvas

Draw your pipeline. Then run it.

A visual editor built on @xyflow/react and a pure-FSM engine. Compose the whole flow as a graph — no YAML, no glue scripts.

1.1 · Compose

The graph is the program.

Add input, agent, and end nodes and connect them with N8N-style arrow edges that show exactly how data flows. Branch, merge, and fan-out in a single view.

  • Branch, merge and parallel fan-out
  • Closed-arrowhead bezier edges
  • Pure-FSM execution engine
localhost:7878/p/orchestrator/canvas
Futsu workflow canvas with a multi-model pipeline
1.2 · Configure

Every node is configurable.

Click a node to pin its runner, write the instruction, and tune parameters. Inline personas and role presets get you from blank node to working step in seconds.

  • Per-node model, temperature & max-tokens
  • Inline persona & role presets
  • Typed input/output ports
node · model call
Futsu node properties panel with a model picker
1.3 · Replay

Replay any run on the canvas.

Every execution is recorded. Scrub the timeline, watch nodes light up in order, and inspect exactly what each step produced.

  • Timeline scrubber over the live graph
  • Per-node status & cost
  • File-based artifacts under .futsu/runs/
run · replay
Futsu run replay with a timeline over the executed graph
Use cases

What teams use Canvas for.

JOB 01

Ship a plan → code → review release pipeline

Plan with Claude, fan out to Claude Code and Codex, gate the merge behind a human checkpoint.

JOB 02

Fan one task out to parallel agents, merge the results

Branch the graph, run both sides at once, and pipe the outputs into a review node.

JOB 03

Replay yesterday’s failed run step by step

Scrub the timeline over the live graph and inspect what every node produced.

Free in early accessBring your own keys — zero markupEverything lands as plain filesNo credit card

Your next pipeline starts on a canvas.

Open a canvas, drop your first nodes, and run it in minutes.