Skip to main content
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.
Add --json for machine-readable output:

​
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.