Skip to main content
Local runs execute a Journey on your own machine using the Reqflo CLI. They’re fast, require no cloud infrastructure, and use your local environment for value and secret resolution. Local runs are the go-to for development iteration, pre-push checks, and quick manual verification.

​
When to use it

  • You’re developing or debugging a journey and want fast feedback without waiting for a cloud run.
  • You want to run a journey against a locally-running service (for example, localhost:3000).
  • You’re iterating on value configuration and don’t need a persistent result record.
  • You’re writing a shell script or local automation and want to run journeys as part of it.
For CI pipelines, scheduled automation, or anything that needs durable results and cloud-managed secrets, use the Cloud Runner instead.

​
Key concepts

Local execution. The CLI compiles the journey into a build artifact and executes it on your machine. No cloud infrastructure is involved unless you add --cloud. Local environment and secret resolution. When a journey references secret references or environment values, local runs resolve them from your local environment — shell environment variables, a local .env file, or local secret configuration. The values are resolved at run time and are never sent to Reqflo’s servers. Environments. You still select an Environment when running locally. The environment provides base URLs and service-level config. If your local setup overrides specific values (for example, pointing base_url at localhost), those overrides take effect based on local environment resolution. Cases and run inputs. Cases work the same way locally as they do in the cloud. Select a case with --case <name> to autofill a known value configuration, or pass individual values with --set key=value.

​
How it works

The CLI authenticates with Reqflo (see reqflo login), fetches the journey definition, compiles it into a build artifact locally, and executes it. Results are printed to stdout in the format you specify.

​
Examples

Basic local run 
reqflo run checkout-flow --env staging --case "Happy path"
Run against a local service 
reqflo run checkout-flow --env local --case "Happy path"
Pass individual values 
reqflo run checkout-flow --env staging --set user_id=usr_abc --set amount=2500
JSON output 
reqflo run checkout-flow --env staging --case "Happy path" --reporter json
Data-driven local run 
reqflo run payment-flow --env staging --data test-data.csv
Local run for pre-push check 
# In a git hook or shell script
reqflo run checkout-flow --env staging --case "Happy path" --reporter json --output results/run.json