Pull your team's flows

Download an environment’s flows into a local cache without running them.

For most workflows, qawolf flows run --env <env> is enough — it pulls the environment’s flows for you when they are not already cached locally. Reach for qawolf flows pull when you want to download the flow files without running them: to inspect them, commit them to a repository, or refresh a stale cache.

Authenticate the CLI first. See Authenticate the QA Wolf CLI.

Pull an environment

1. Find the environment’s ID in your QA Wolf workspace under Workspace settings → Environments.

2. Pull the flows:

   qawolf flows pull --env staging
   

   The CLI writes flows to .qawolf/staging/ by default. To use a different destination, pass --out:

   qawolf flows pull --env staging --out ./snapshot
   
3. List the pulled flows:

   qawolf flows list
   

What pull writes

Inside .qawolf/<env>/, the CLI stores:

• the flow source files
• a manifest tracking what was pulled and when
• a .env file with the environment’s variables, loaded automatically by qawolf flows run

Refresh a pulled environment

Run qawolf flows pull --env <env> again. The CLI prompts before overwriting any file that has been modified locally. To skip the prompt and overwrite, pass --yes:

qawolf flows pull --env staging --yes

List flows on the platform

To see what is available on the platform without pulling, use --remote:

qawolf flows list --remote
qawolf flows list "checkout/**" --remote

What’s not pulled

File assets stored in QA Wolf cloud storage are not pulled. Web flows that read paths from QAWOLF_*_DIR environment variables cannot run locally until the assets are available on the machine. Mobile flows reference the APK or IPA build through an environment variable — make sure that path is set before running.