Skip to content

Live Sessions#

Live Sessions bridge the gap between the web-based visual editor and your local infrastructure and is primarily used for development purposes. By connecting a local runner to a Live 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 Live Session:

1. Start Session ⏻#

The power button controls the state of the Live Session.

  • Green: The Live Session is active and listening for a runner connection.
  • Action: Click to start a new Live Session.

2. Copy Session Token 📋#

Once a Live Session is active, a unique, secure handshake token is generated.

  • Action: Click to copy the Session Token to your clipboard.
  • Usage: Paste this token into your local terminal to start the runner (e.g., actrun start --token <PASTE_TOKEN>). This authorizes your local machine to join the specific Live Session.

3. Execute Graph ▶#

Triggers the execution of the current flow within the Live Session.

  • Disabled: As shown in the tooltip "No Runner Connected," this prevents execution until a runner joins the session.
  • Enabled: Once your local runner connects, this becomes active. Clicking it sends the graph logic to your machine for immediate execution.

4. Encryption Status ( 🔒 )#

The padlock icon indicates the security state of the Live Session. It is a visual reminder that all communications are encrypted end-to-end between your browser and local runner.

Encryption#

Live Sessions prioritize the security of your infrastructure. Even though the graph is edited in the browser, the execution utilizes strict End-to-End (E2E) Encryption.

Zero-Knowledge Architecture#

  • Encrypted Tunnel: 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.

It is important to note that credentials are never transmitted over this connection, not even encrypted. Credentials are always loaded by your runner from your machine, so there is no need to even send them to the browser.