Skip to main content
Examples use npx @xerg/cli@latest. If you installed the CLI globally, substitute xerg. For dashboard, API, hosted MCP, Slack, website, or documentation availability, check the Xerg status page before debugging local configuration.

Common problems

Hermes profile and identity recovery

An invalid explicit/sticky profile does not fall back to another home. Check xerg doctor --runtime hermes --hermes-profile <name> --details and select the intended existing source. Do not delete or reset a damaged/missing identity registry to force upload; restore validated bindings or resolve retained and destination evidence. A busy registry fails after bounded waiting, not by breaking an uncertain lock. Divergent copies block a complete rollup and new uploads for that group. Inspect each candidate non-additively; do not select one arbitrarily or create another hosted identity. Combined rollups remain local-only. Ambiguous legacy caches require resolution or re-audit, whereas an existing prepared single-source Push file preserves its original retransmission metadata during registry failure.

Advanced authentication recovery

If browser pairing is unavailable, npx @xerg/cli@latest login --replace opens Settings and masks the workspace key pasted into the terminal. This is a recovery path, not normal onboarding. XERG_API_KEY and ~/.xerg/config.json are intended for non-interactive CI or managed automation.

Debug in the right order

  1. Run npx @xerg/cli@latest doctor.
  2. Run the plain audit without extra flags.
  3. Add --details for the full human report, or --compare, --json, or --push once the base audit works.
  4. If the data is remote, validate SSH or Railway access separately before debugging Xerg flags.
For QM, start with doctor --runtime qm because bare doctor intentionally does not probe databases or Fly apps.

Get help