Skip to main content
BAP workflows are YAML files that define a sequence of browser steps. Record them interactively, edit the YAML to add parameters and assertions, then replay them deterministically.

Recording a Workflow

1

Start recording

Recording state is persisted to ~/.bap/recording.json so it survives across CLI invocations.
2

Execute your browser commands as normal

bap goto https://store.example.com bap act click:text:"Add to cart" bap act

YAML Format

A recorded workflow produces YAML like this:

Parameters

Add parameterized values so workflows can be reused with different inputs:
Run with parameter overrides:

Assertions

Add post-step assertions to validate workflow correctness:
Three assertion types are available:

Step Labels

Add human-readable labels for clearer output:

Repeat and Conditionals

Repeat a step N times

Repeat until a condition is met

Conditional execution

Macros

Define reusable step sequences:

Error Handling

Control what happens when a step fails:

Per-Step Timeout

Fused Observation

Add observe: true to any step to get a page observation after it executes:

Managing Workflows

Workflows are saved to ~/.bap/workflows/ as YAML files.

Step Types