Debug with breakpoints
Pause execution at a node, step, inspect agent memory, and manage breakpoints across graphs.
A breakpoint pauses debug execution when the VM reaches the marked node. Mark nodes in the editor, then start the run with Debug rather than Run — breakpoints have no effect on a normal run.
- The Debug rail holds the execution controls, with Breakpoints and Memory as subtabs.
- Breakpoints lists the marked nodes for the open graph, and can sync them with the server.
- Memory shows the agent memory published and referenced while the run is paused.
- /breakpoints collects every breakpoint saved in this browser, across all graphs, so you can clear stale ones.
Related
- Run a graphRunning & debuggingSupply the input, clear validation, start the run, and find it afterwards.
- Live runs, suspension, and resumingRunning & debuggingWhere a currently-executing run shows up, why its history page can 404, and how suspended runs continue.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
More in Running & debugging · Search all help