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

> Check a Mo session's state and findings.

Get the session state and counts for test cases, bugs, and verdicts. Add
`--full` for the findings and latest message.

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

## Arguments

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

## Output

By default, the command prints:

```json theme={null}
{
  "sessionId": "<session-id>",
  "state": "idle",
  "displayState": "ready",
  "sessionState": "idle",
  "webUrl": "https://app.momentic.ai/mo/sessions/<session-id>",
  "counts": {
    "testCases": 4,
    "bugs": 2,
    "verdicts": 4
  }
}
```

`--full` replaces `counts` with `findings.testCases`, `findings.bugs`, and
`findings.verdicts` arrays. It also adds `latestMessage` (`null` when
unavailable). Test cases and bugs are limited to the main agent. Verdicts are
the signed-off outcomes from sub-agents.

`displayState` is the session's state as the UI shows it: `needs_you`,
`running`, `waiting_on_agents`, `failed_start`, `cancelled`, `ready`, or
`sleeping`. It is the field to prefer. `state` is a legacy alias of
`sessionState`, and both carry the lifecycle state (`starting`, `working`,
`waitingOnUser`, `waitingOnAgents`, `idle`, or `stopped`). Servers running an
earlier API report the display word in `state` instead.
[`qa read`](/docs/cli-reference/mo/commands/read) and `qa report` report the
identical `displayState`, so scripts can compare the commands directly.

## Examples

List bug names:

```bash theme={null}
set -o pipefail
qa status "$session_id" --full | jq -r '.findings.bugs[].name'
```

Poll a session until it stops running, then list the bugs it found:

```bash theme={null}
set -o pipefail
while :; do
  state=$(qa status "$session_id" | jq -r '.displayState // .state') || exit $?
  [[ "$state" == running || "$state" == waiting_on_agents ]] || break
  sleep 10
done
qa status "$session_id" --full | jq -r '.findings.bugs[].name'
```

## Notes

* `status` returns immediately. Use
  [`qa read --timeout`](/docs/cli-reference/mo/commands/read) to wait for output.
* Send input to a `needs_you` session with
  [`qa send`](/docs/cli-reference/mo/commands/send).


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