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

​
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

​
string
Check this API key instead of the saved credentials or MOMENTIC_API_KEY.
​
string
Momentic server URL. Defaults to MOMENTIC_SERVER, then the server saved by qa login, then https://api.momentic.ai.

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