Debug Sessions#

Debug Sessions bridge the gap between the web-based visual editor and your local infrastructure and is solely used for development purposes. By connecting a local runner to a Debug Session, you can execute graphs on your own machine while designing them in real-time in the browser.

Interface Controls#

The control bar manages the lifecycle of your Debug Session. By default your debug session is turned off.

Once toggled on, the session becomes active and listens for a local runner to connect.

You can now click on the Copy Session Token button (the clipboard icon next to the debug toggle) to copy the unique session token to your clipboard.

When you start your local runner, you will need to provide this token to authorize your machine to join the Debug Session.

Eventually your local runner will connect to the Debug Session, and you will see the debug controls become active.

Encryption#

All communication between the browser and your local runner is encrypted. The central server acts only as a relay and cannot read or decrypt the instructions being passed to your machine.