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

> ## Agent Instructions
> The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file.
> For an unattended setup, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell.
> Mo is the AI QA engineer, a separate product from the YAML test framework: its npm package and CLI are `qa` (not `mo` — `npx mo` is a different project). Install with `npm install -g qa`, authenticate the same MOMENTIC_API_KEY way, install repo skills with `qa skills -y`, and start a session with `qa start "<brief>"` or `qa <url>`. Docs: https://momentic.ai/docs/mo.md.
> You cannot complete the browser sign-in yourself. Read the API key from the exact MOMENTIC_API_KEY environment variable (similarly named vars like BILT_MOMENTIC_API_KEY are ignored), or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx momentic skills --yes` (or `npx momentic-mobile skills --yes` for mobile).
> Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags.
> Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators. Physical devices are not supported.

# qa doctor

> Check the qa CLI installation and PATH for possible problems.

`qa doctor` checks which `mo` and `qa` executables your shell finds, how the
running copy was installed, whether credentials are saved, and whether the
Momentic server is reachable. Include the output when you report a CLI problem.

```bash theme={null}
qa doctor
```

Add `--json` for machine-readable output:

```bash theme={null}
qa doctor --json
```

## Checks

The report renders labeled sections with a status for each check:

* `qa`: the CLI version (checked against the latest release), the Node.js
  version, the install method (`npm` or `standalone`), and the resolved binary
  path.
* `Executables on PATH`: every `qa`, `mo`, and `momentic` executable on your
  `PATH`, in order. On macOS and Linux, the first match for each name is the one
  your shell runs. Each entry shows the executable's real path, so npm launcher
  shims (`cli.cjs`) are distinguishable from standalone binaries.
* `Authentication`: the auth directory, the saved credentials file, and a live
  check of the API key against the Momentic server.
* `Connectivity`: HTTPS reachability, TLS verification, and clock skew against
  the server.

Warnings and problems print as a numbered list at the end, each with the fix.
The command exits non-zero when any problem is found.

## Options

<ParamField path="--api-key" type="string">
  Check this API key instead of the saved credentials or `MOMENTIC_API_KEY`.
</ParamField>

<ParamField path="--server" type="string">
  Momentic server URL. Defaults to `MOMENTIC_SERVER`, then the server saved by
  `qa login`, then `https://api.momentic.ai`.
</ParamField>

## Warnings

`qa doctor` warns when:

* A legacy Momentic `mo` executable is on `PATH`. `mo` was the command's name
  before 0.18. When the running install is still named `mo`, `mo upgrade` moves
  it to `qa`. Remove any other stale `mo` file; curl installs left one at
  `$HOME/.local/bin/mo`.
* Multiple executables with the same name are on `PATH`. On macOS and Linux, the
  earlier directory wins, so a stale copy can shadow a newer install. Remove the
  old copy or reorder `PATH`, then run `hash -r` in the current shell so it
  forgets the old location.
* `MO_BINARY_PATH` is set. The npm launcher runs that binary instead of the
  installed one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.