qawolf flows run --env <env_id> 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 the QA Wolf app. Open Workspace settings → Environments and select the environment. Copy the
id query parameter from the page URL: https://app.qawolf.com/<team_slug>/settings/environments?id=<env_id>. Use that value, not the environment’s display name.2
Pull the flows:The CLI writes flows to
.qawolf/<env_id>/ by default. To use a different destination, pass --out:3
List the pulled flows:
What pull writes
Inside .qawolf/<env_id>/, the CLI stores:
- the flow source files
- a manifest tracking what was pulled and when
- an
assets/directory with the environment’s file assets from team storage, wired up so flows resolve them locally - a
.envfile with the environment’s variables, loaded automatically byqawolf flows run
Refresh a pulled environment
Runqawolf flows pull --env <env_id> again. The CLI prompts before overwriting any file that has been modified locally. To skip the prompt and overwrite, pass --yes:
List flows on the platform
To see what is available on the platform without pulling, use--remote:
What’s not pulled
Mobile app binaries are not downloaded. Mobile flows reference the APK or IPA build through an environment variable, so make sure that path points to a build available on the machine before running. Flows that read paths from runner-onlyQAWOLF_*_DIR environment variables also cannot resolve those paths locally; qawolf doctor flags both cases.