> ## 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, first check whether Claude Code already has the Momentic plugin. With the plugin, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools none` and ignore any CLI skills-install suggestion in its output. Otherwise, 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, separate from repository YAML tests. With the Momentic plugin, use bundled mo-qa and hosted OAuth by default. Without the plugin, install only mo-qa with `npx -y qa skills --target <agent>`. Keep the requested interface. Otherwise, use hosted tools for web or mobile, including private web targets with an existing Connector. Run sessions that need a new tunnel with the qa CLI. If you can't run commands on the machine that reaches the target, ask the user to start the tunnel there, then use hosted tools unless you lack them or the CLI was requested. For a requested hosted session, use an online Connector and pass its name as access, not a CLI tunnel ID. If none is online, ask the user to run `npx -y qa tunnel start --name <name> <address>` on a machine that reaches the target and wait. Do not run login or tunnel commands for them. For a requested hosted session, report unavailable tools or authentication failures without starting a CLI session. For coding-agent bridge setup, ask the user to complete `npx -y qa login`, then add momentic-hosted as a stdio server running `npx -y qa mcp`. Plugin users must explicitly opt in and disable their hosted plugin entry before adding the bridge. Claude.ai/ChatGPT connectors keep https://mcp.momentic.ai with OAuth. After hosted testing completes, read the report and summarize findings and uncovered requirements. Call `momentic_mo_stop_session` only when the user asks or agrees. For CLI sessions, unless the user wants more testing, export the report, run `qa stop <id> --subagents` even if export fails, then summarize. The CLI is qa, not mo. Docs: https://momentic.ai/docs/mo/quickstart.md.
> Ask the user to complete browser sign-in. For local CLI tools, use the exact MOMENTIC_API_KEY environment variable. If it is absent, ask the user to create a key at https://app.momentic.ai/settings/api-keys and set it in the agent's environment. Never print the key or ask the user to paste it into chat.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Claude Code users with the Momentic plugin should use its bundled skills and skip CLI skills installation. Otherwise, run `npx momentic skills -y --target <agent>` or `npx momentic-mobile skills -y --target <agent>`. Both install momentic-test, momentic-maintain, and momentic-spec with web/mobile references. Use the running agent's target. The Momentic plugin also includes mo-qa; qa skills installs only mo-qa.
> 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.

# qa cases

> List and describe the test cases Mo observed.

While Mo tests, it records each flow it exercises as a test case with its
account, prerequisites, steps, and status. A session started with
`--no-test-cases`, or one where Mo has not recorded a case yet, lists none.

## cases list

```bash theme={null}
qa cases list <session-id> [--output <file>]
```

Prints a JSON array of the session's current cases, in the order Mo recorded
them:

```json theme={null}
[
  {
    "id": "6d0f1c3a-2b4e-4f8a-9c1d-7e5b3a2f9c10",
    "name": "Check out with a saved card",
    "status": "issues_found",
    "statusReason": "Checkout fails",
    "account": "QA buyer",
    "description": "Pay for a cart with the buyer's saved card.",
    "bugs": [{ "id": "bug_3f9a1c2e", "name": "Checkout fails" }],
    "stepCount": 5
  }
]
```

`status` is `running`, `verified`, `issues_found`, or `blocked`. `statusReason`
is the filed bug or evidence for `issues_found`, the blocker for `blocked`, and
`null` otherwise or when Mo recorded neither. `account` is empty when the case
runs signed out. `bugs` lists filed bugs only, and each id works with
[`qa bugs describe`](https://momentic.ai/docs/cli-reference/mo/commands/bugs). Linked bugs may take a
few more minutes to appear under a test case while they are verified.

## cases describe

```bash theme={null}
qa cases describe <session-id> <case> [--output <file>]
```

Prints one case with its prerequisites and the steps of one run, in order.
Checks are steps too. `<case>` is the `id` or the exact name. An unknown case
fails and lists the ids and names of up to 20 of the session's cases.

```json theme={null}
{
  "id": "6d0f1c3a-2b4e-4f8a-9c1d-7e5b3a2f9c10",
  "name": "Check out with a saved card",
  "status": "issues_found",
  "statusReason": "Checkout fails",
  "account": "QA buyer",
  "description": "Pay for a cart with the buyer's saved card.",
  "bugs": [{ "id": "bug_3f9a1c2e", "name": "Checkout fails" }],
  "evidence": "The order page shows \"Something went wrong\".",
  "prerequisites": ["The cart has at least one item."],
  "steps": [
    {
      "text": "Open the cart",
      "startedAt": "2026-10-28T17:20:02.000Z",
      "finishedAt": "2026-10-28T17:20:05.000Z"
    },
    {
      "text": "Pay with the saved card",
      "startedAt": "2026-10-28T17:20:41.000Z",
      "finishedAt": "2026-10-28T17:20:58.000Z"
    },
    {
      "text": "Check the order confirmation appears",
      "startedAt": "2026-10-28T17:21:00.000Z",
      "finishedAt": "2026-10-28T17:21:09.000Z"
    }
  ]
}
```

`evidence` is what settled the status. It is `null` while the case is running or
when Mo recorded none.

## Options

**--output \<file>** `string`

Write the JSON to this file instead of stdout and print the file's path.


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