> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qawolf.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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>`](/qawolf/local-execution/run-flows-locally) 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.

<Check>
  Authenticate the CLI first. See [Authenticate the QA Wolf CLI](/qawolf/local-execution/authenticate).
</Check>

## Pull an environment

<Steps>
  <Step>
    Find the environment's ID in your QA Wolf workspace under **Workspace settings → Environments**.
  </Step>

  <Step>
    Pull the flows:

    ```bash theme={null}
    qawolf flows pull --env staging
    ```

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

    ```bash theme={null}
    qawolf flows pull --env staging --out ./snapshot
    ```
  </Step>

  <Step>
    List the pulled flows:

    ```bash theme={null}
    qawolf flows list
    ```
  </Step>
</Steps>

## What `pull` writes

Inside `.qawolf/<env>/`, 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 `.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`:

```bash theme={null}
qawolf flows pull --env staging --yes
```

## List flows on the platform

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

```bash theme={null}
qawolf flows list --remote
qawolf flows list "checkout/**" --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-only `QAWOLF_*_DIR` environment variables also cannot resolve those paths locally; `qawolf doctor` flags both cases.