> ## 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.
> You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, 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 skills@latest add momentic-ai/skills`.
> 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.

# mo status

> Get a snapshot of a Mo session, including its findings.

Check where a session stands without reading its transcript. `status` returns
the run state, the latest message, the dashboard URL, and everything Mo has
reported so far: test cases, bugs, exercised controls, and bug bash verdicts.
Use it to poll a session or to pull the [report](/docs/mo/reports) into a script.

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

## Arguments

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

## Output

The command prints one pretty-printed JSON object:

```json theme={null}
{
  "sessionId": "<session-id>",
  "state": "active",
  "latestMessage": {
    "id": "<message-id>",
    "role": "assistant",
    "text": "Finished the checkout flow. Filed 2 bugs.",
    "createdAt": "2026-09-02T04:12:33.000Z"
  },
  "webUrl": "https://app.momentic.ai/...",
  "findings": {
    "testCases": [],
    "bugs": [],
    "controls": [],
    "verdicts": []
  }
}
```

* `state` is `active`, `completed`, `cancelled`, or `failed`, or `null` when no
  run state is available for the session.
* `latestMessage` is `null` when the session has no visible messages.
* `findings` arrays grow as Mo works. Each bug entry includes a name, summary,
  expected and actual behavior, and reproduction steps.

## Examples

List the bugs Mo has filed so far:

```bash theme={null}
mo status "$session_id" | jq -r '.findings.bugs[].name'
```

Wait until the session's run finishes:

```bash theme={null}
until [[ $(mo status "$session_id" | jq -r .state) != active ]]; do sleep 30; done
```

## Notes

`status` is a point-in-time snapshot and never blocks. To wait for Mo's next
output, use [`mo read --timeout`](/docs/cli-reference/mo/commands/read) instead.
