Skip to main content

Debugger

The debugger lets you watch a diagram while it is being run and debugged by someone else, typically the diagram agent in the sidebar or an external AI client that is connected to the MCP server and uses its run tools. You see what the other side sees: where the run stands in the diagram and what the variables are. You can also take the controls yourself.

The debugger is a view of its own and never changes the diagram.

Opening the debugger​

Click the eye button in the run controls of the diagram editor to open the debugger. In the debugger the pencil button in the toolbar takes you back to the editor.

The agent chat is on the left, as in the editor, and it stays the same conversation when you switch between the two views. If the agent starts a run while you are in the debugger, you see it immediately.

What you see​

  • The diagram is shown read-only, so nothing can be moved or deleted by accident. The node the run stands at is marked like a selected node. Scrolling still works.
  • Run lists your recent runs. The debugger follows the newest running run by itself; pick another one from the list to stay on it, and tick Follow the newest run to let it follow again. Below the list you see the status (running, paused, finished, failed or stopped), the diagram, the end node reached, the number of executed steps and, when the run is paused inside a module, the call stack.
  • Variables lists the variables of the run with their current values. When a value changes, its row flashes briefly, so you can see what the last step did. Long values are shortened, and secrets are masked.

While a run is executing, the variables are collected from the steps it has taken so far. As soon as it pauses or ends, the values are read from the run itself.

Controls​

The toolbar of the debugger controls the followed run. A button is only enabled when it makes sense.

ButtonDoesAvailable
StepExecutes one node and pauses againwhile the run is paused
ContinueRuns on until the next breakpoint or the endwhile the run is paused
Stop runEnds the runwhile the run is not over

A run is paused when it was started step by step or reached a breakpoint. If the agent and you press a button at the same moment, one of you gets a short message that the run was not in the expected state; the view then shows what actually happened.

Good to know​

  • You only see your own runs.
  • Breakpoints are set when the run is started (by the agent or the MCP client), not in the debugger.
  • The debugger shows the diagram that was started. When a run is inside a module, the module is not shown on the canvas, the call stack names it.
  • The view updates every half second while it is open and stops asking when you leave it.
  • If the agent edits the diagram that is shown, the debugger reloads it.