> ## 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` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell.
> You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, 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

> Print diagnostics for the Mo CLI installation and PATH.

Use `qa doctor` to check which `mo` and `qa` executables your shell finds, how
the running copy was installed, and whether credentials are saved. 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
```

## Output

The report lists the CLI version, the install method (`npm` or `standalone`),
the resolved binary path, the Node.js version, and the auth state: whether
`MOMENTIC_API_KEY` is set or credentials are saved to the auth file.

The `on PATH` section lists every `mo`, `qa`, and `momentic` executable on your
`PATH`, in order. 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.

## Warnings

`qa doctor` warns when:

* Multiple executables with the same name are on `PATH`. 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.
* A `mo` executable is on `PATH`. `mo` was the command's name before 0.18;
  remove the stale file, which curl installs left at `$HOME/.local/bin/mo`.
* `MO_BINARY_PATH` is set. The npm launcher runs that binary instead of the
  installed one.