Product tour

Inside the workflow workspace.

Follow a process from editable steps to inspectable results. Screenshots show the desktop app; the short animations illustrate how the tools work.

Download Bandura Follow the getting-started guide

Graph and code

Two views of the same process.

Edit the steps and routing visually, or work directly with the YAML in your repository.

An illustration of graph and code editing over one workflow file.

A close view of connected workflow nodes on the Bandura graph canvas — The graph makes step order and routing visible.

Results and variables

Inspect the values each step uses.

Open the resolved request and response, then inspect the values captured for later steps.

The node inspector displaying a resolved POST request with headers and a JSON body — Inspect the actual request produced by a step.

The variables panel listing workflow inputs and captured values with source labels — Trace a captured value back to the step that produced it.

Explore the inspector panels →

Optional model assistance

Start a workflow from a description.

Connect your own model to help draft steps. Review the generated workflow and run it against sample inputs.

A password-reset workflow on the graph after generation and a successful sample run — A generated workflow remains editable in the graph and YAML views.

Read the generation guide →

For API workflows

Keep requests aligned with your spec.

Compare a workflow with an OpenAPI definition and review suggested fixes when endpoints change.

OpenAPI drift detection uses a deterministic comparison and does not require a model.

See how drift detection works →

From the current build

Screenshots of the app as it is today.

Captured from the real desktop app, the same build the end-to-end suite runs against. No mockups, no repaints.

Graph editor

Model the scenario the way you'd whiteboard it.

Login, capture the token, spend it downstream. The graph is the test. Every node in it is still real, editable code underneath.

Execution

Runs you can watch, then interrogate.

Nodes light up as they pass or fail, and any one of them will show you the exact request and response it produced.

The Bandura debugger paused at a breakpoint on the create-order node: the upstream login, product, and stock-check nodes passed in green, the paused node ringed in amber with a pause badge, and the variables panel showing the captured access token and product data

Step-through debugging

Pause mid-flow and see exactly what happens next.

Set a breakpoint and run: execution halts before that node fires, with the variables panel showing what the next call is about to spend. Breakpoints live in your editor, never in the .aether file.