Executors are responsible for running the graphs in Rivet. The executor can be chosen using the dropdown in the menu bar of the application.
There are 3 possible executors in use at any one time:
This is the default executor. Rivet itself is a browser application running in a web view. The browser executor runs in the same process as the Rivet application, and runs the graph there. This is the simplest executor to use, but is limited by the capabilities of the browser (and a few file-system APIs).
This executor runs a separate Node.js process to execute graphs, and communicates with it using the remote debugger protocol. This executor is more powerful than the browser executor, but can be more temperamental and does not support every feature of the browser executor yet.
This executor connects to a remote Rivet server to execute graphs. It requires the remote debugger to be set up on another application, and requires that
dynamicGraphRun is implemented on the remote server, so that the graph shown in the Rivet application can be ran remotely. You may also enable
allowGraphUpload on the remote executor to allow the graph to be uploaded to the remote server, and then ran there.
To use the remote executor, connect via the Remote Debugger option in the dropdown of the Rivet action bar.