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

# Run your first Mo session

> Start a Mo session against a URL or an app build, read the report, and triage the bugs it reproduced.

Mo needs no test suite and no code in your repository. Give it a running target
and a brief.

<Steps>
  <Step title="Open the composer">
    Open Mo in the Momentic app and select the target.
    Select **Web** and paste the exact URL, including the path of the area you
    want checked, or select an uploaded mobile build. A staging or preview URL is
    fine.
  </Step>

  <Step title="Write a narrow brief">
    Name one area, the account to sign in with, and the actions Mo must not take:

    ```text theme={null}
    Test the checkout flow on https://staging.example.com/cart.
    Sign in with the staging QA buyer. Do not submit a payment and do not delete
    an order.
    ```

    Mo asks you for anything it still needs before it starts. See
    [write a good brief](/docs/mo/brief) for the full field list.
  </Step>

  <Step title="Watch the run">
    Test cases and bugs appear while the session continues, and the first bugs
    can appear within minutes. Open the transcript of any sub-agent to see what
    it did, or message Mo to change the scope mid-run.
  </Step>

  <Step title="Read the report">
    The report holds a verdict per case and a bug entry for each failure a
    reproducer agent confirmed from a clean browser. See
    [session reports](/docs/mo/reports).
  </Step>

  <Step title="Triage what it found">
    Accept a bug, or mark it works as intended and give the reason. That reason
    goes to the knowledge base, so a later session does not report the same
    intended behavior. See [triage](/docs/mo/triage).
  </Step>
</Steps>

## Start a session from your coding agent

Install the Mo skill, then ask the agent to run the pass:

```bash theme={null}
npx skills add https://github.com/momentic-ai/skills --skill mo-qa
```

```text theme={null}
/mo-qa bug bash my new feature on <branch>
```

The skill installs and authenticates the `mo` CLI, writes the brief, starts the
session, and follows it. See [install Mo skills](/docs/mo/skills) and
[use the Mo CLI](/docs/mo/cli).

## What a pass looks like

A file storage and sharing product ran Mo against staging before a release. The
team wrote no tests for the pass.

* The brief was the release scope and one staging URL.
* The session agent planned the coverage and dispatched explore agents over the
  product areas in the scope.
* At its widest the session held 116 agents at once, each with its own hosted
  browser.
* 27 bugs reached the report, each one reproduced by a bug reproducer agent from
  a clean browser, with expected behavior, actual behavior, reproduction steps,
  and a recording.
* The pass ran in an afternoon, and it covered work the team estimated at two
  days of manual QA.

## Next

<CardGroup cols={2}>
  <Card title="Run a session" icon="play" href="/docs/mo/sessions">
    Sign-in, test data endpoints, schedules, and what a pass costs.
  </Card>

  <Card title="Use cases" icon="list-check" href="/docs/mo/use-cases">
    Pull requests, Vercel previews, local branches, and mobile builds.
  </Card>

  <Card title="How Mo works" icon="sitemap" href="/docs/mo">
    The agents in a session, the targets, and the limits.
  </Card>
</CardGroup>