> ## 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 report

> Export a Mo session's findings and reproduction videos.

Export the session report to a local directory, with one file per findings
category and any available bug recordings. Give the directory to a coding agent
to investigate or fix the reported bugs.

```bash theme={null}
qa report <session-id>
```

## Arguments

<ParamField path="<session-id>" type="string" required>
  The session to export.
</ParamField>

## Options

<ParamField path="--output <directory>" type="string">
  Directory to write the report and videos to. Defaults to
  `MOMENTIC_ARTIFACTS_DIR/mo-report-<session-id>` when that variable is set,
  or `.momentic-artifacts/mo-report-<session-id>` otherwise.
</ParamField>

<ParamField path="--require-idle" type="boolean">
  Only export when Mo is idle and all sub-agents are done. Checks once and exits
  without writing otherwise; it does not wait.
</ParamField>

## Output

The command prints the output directory. Inside it, `report.json` is the
manifest:

```json theme={null}
{
  "sessionId": "<session-id>",
  "findings": {
    "bugs": "bugs.json",
    "testCases": "testCases.json",
    "verdicts": "verdicts.json",
    "triage": "triage.json"
  },
  "artifacts": [{ "bugName": "...", "path": "..." }]
}
```

Read every file `findings` names; newer servers can add categories. `artifacts`
holds each recording download as `{ bugName, path }` or `{ bugName, error }`.

| File | Contents |
| - | - |
| `bugs.json` | Reviewed bugs: expected and actual behavior, reproduction steps, recording metadata. |
| `testCases.json` | The intended coverage: preconditions, outline, and acceptance criteria per case. |
| `verdicts.json` | The verification outcome, confirmed behavior, and coverage gaps per case. |
| `triage.json` | Human dispositions (accepted, duplicate, works as intended). No entry means open. |

## Examples

Export once the session finishes:

```bash theme={null}
qa report "$session_id" --require-idle --output mo-report
```

List every bug name:

```bash theme={null}
jq -r '.[].name' mo-report/bugs.json
```

## Notes

Exporting does not rerun anything. To compare a recheck, `qa send` the recheck
request, wait for idle, and export again into a second `--output` directory.


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