Path Tracing
Trace data flow through your graph — from any output port back to the inputs that feed it. Use paths to debug, document, and reason about complex workflows.
What is a path?
A path is a saved trace through your graph: a chain of nodes and edges that produce a particular output. Paths are visual, named, and persist with the graph. They're useful when:
- You want to highlight the data flow that produces a specific metric.
- You're reviewing a teammate's graph and need to understand what feeds what.
- You're debugging an unexpected output and want to walk back to its source.
Entering path-draw mode
Click the Path tool in the canvas toolbar (or press P). The cursor switches to crosshairs and the Paths panel slides in at the top-right of the canvas.
Drawing a path
-
Click an output port
Pick the port whose data you want to trace. Connectify highlights every node and edge that feeds into it.
-
Optionally narrow the source
Click an input port further up the chain to bound the path. Everything between source and target lights up; everything else dims.
-
Save and name the path
Click Save in the Paths panel. Give it a name like "Eval loss → augmented input" so you can re-open it later.
The Paths panel
The Paths panel lives at the top-right of the canvas as a floating overlay. It lists every saved path on the current variant. Click a path chip to highlight it on the canvas; click again to clear.
Variants get their own paths
Paths are scoped to the variant they were drawn on. When you switch variants the panel reloads with that variant's paths.
Hiding the panel
Close the Paths panel with the X in its header. A subtle banner appears on the canvas reminding you the panel is hidden — click the banner to bring it back. Closing the panel doesn't delete paths; it only hides the overlay.
Common patterns
Documenting a result
After running a graph and getting a number you want to ship, draw a path from that output back to the inputs that produced it. Save it with the metric name. The next person who opens the graph can click the path chip and instantly see provenance.
Debugging
If a node's output looks wrong, draw a path from that output. Walk the highlighted edges back, checking the Run Data tab in the Inspector on each node, until you find where the values diverge.
Comparing variants
Draw the same path on two variants. The structure may differ — that's the point. Side-by-side paths make ablation differences obvious.