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

# Choose how to run Mo

> Run Mo against a release, a manual bug bash, an open-ended brief, a test plan, a schedule, a repository change, a local branch, or a mobile app build.

A Mo session takes the same kind of brief in every case below. What changes is
the target, the source of the brief, and when the pass runs.

## When to use Mo

### Bug bash a release

Point Mo at a staging or preview build with the release scope. Mo plans the
cases, runs them in parallel, and files the bugs it reproduced. Use it where the
team has no suite for the pass and nobody free to run it by hand.

### Start a run from a prompt

```bash theme={null}
mo start "Test the checkout flow on https://preview.example.com. Sign in with the staging QA buyer. Do not submit payment."
```

Mo asks for anything it still needs, then plans the cases itself.

### Schedule repeated runs

Use a schedule for a nightly pass of the main flows. Each occurrence starts a
new session from the same prompt. See
[repeat a session on a schedule](/docs/mo/sessions#repeat-a-session-on-a-schedule).

### Run Mo on a pull request

With the Momentic GitHub App installed, Mo takes the preview URL for the branch
and scopes the session to the change. Use it on every change, and keep a
scheduled session for the wider coverage. See
[use GitHub context](/docs/mo/integrations#use-github-context).

## What to point Mo at

### Test a mobile app

Upload the build to a channel and tag as you do for a Momentic mobile test, then
select it in the composer. Give no URL, and describe the flows and accounts
instead. Mo installs the build on a remote simulator or emulator. See
[iOS app setup](/docs/platforms/ios/app-setup) and
[Android emulators](/docs/platforms/android/emulators).

### Test from an existing spec or test plan

Start a session, upload the plan to it, then point Mo at the uploaded file:

```bash theme={null}
remote_path=$(mo upload --session-id <session-id> ./release-plan.md)
mo send --session-id <session-id> "Test the plan at $remote_path."
```

Mo derives the cases from the document. A Confluence page works the same way
once Atlassian is connected.

### Use read-only repository context

Connect a GitHub repository, then name the change instead of describing it:

```bash theme={null}
mo start "Check the checkout change on https://preview.example.com." --repository owner/name
```

Mo reads the repository as read-only context.

### Test a Vercel preview

Connect Vercel in settings > Integrations, leave deployment protection on, and
give the preview URL in the brief:

```bash theme={null}
mo start "Check the checkout flow on https://shop-git-checkout-acme.vercel.app."
```

Mo tests the deployment you name, so a preview run leaves production alone. See
[test a protected target](/docs/mo/integrations#test-a-protected-target).

### Test a local branch

Start a tunnel for the local branch:

```bash theme={null}
mo tunnel start localhost:3000
```

Use the tunnel ID with `mo start`, and keep `http://localhost:3000` as the exact
URL in the brief. See
[test a local build through a tunnel](/docs/mo/cli#test-a-local-build-through-a-tunnel).

Some ways of running Mo are not available yet. See
[not available yet](/docs/mo#not-available-yet).