Skip to main content
The CLI runs flows that already exist. Create coverage first through Quick start — qawolf flows pull needs an environment that already has flows in it.
1

Install the CLI

Requires Node.js 20.19 or later, or download a standalone binary from GitHub Releases.
2

Sign in

Sign in through a browser or with an API key. In CI or an agent sandbox, set QAWOLF_API_KEY instead.
Confirm the connection with qawolf auth whoami.Read more: Authenticate the QA Wolf CLI.
3

Pull your flows

Find your environment with qawolf --json environment find, then pull its flows and install what they need to run.
Read more: Pull an environment and Install runtime dependencies.
4

Run them

On your machine:
The CLI exits 0 when every flow passes and 1 when one or more fail. See exit codes for the rest.On QA Wolf infrastructure:
Select flows by id, by --tag, or both.Read more: Run flows locally.
If a step fails, run qawolf doctor:
It reports the CLI version, the Node.js version, credentials, connectivity to QA Wolf, and the installed browsers. Read more: Diagnose problems. For coding agents. The CLI ships a qawolf-cli agent skill covering every command, its read or write kind, and the conventions that matter — pass --json for stable output, and terminate interactive runners, which bill while they run. Agents such as Claude Code, Codex, Cursor, and Gemini CLI can use it. It’s included in the @qawolf/cli package under skills/qawolf-cli. See the CLI command reference for every command, flag, and exit code.
Before using a command whose flags you don’t know, run qawolf <command> --help. The installed CLI always matches its own version.
Last modified on September 17, 2026