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

# Custom fields

> Add your own fields, such as severity or product area, that Mo fills in on reproduced bugs based on the descriptions you write.

Use custom fields when your team triages findings by criteria Mo does not report
on its own, so each bug arrives already labeled.

## Add a field

1. Go to **Settings > Mo > Custom fields**.
2. Click **Add field** and fill in:
   * **Name**: the key the value is stored under, such as `Severity`.
   * **Description**: how Mo should fill out the field.
   * **Field type**: the kind of value Mo returns.
3. For **Select** and **Multiselect**, add options. Give each option a name and
   a description of when Mo should choose it.

| Type | Value Mo returns |
| - | - |
| Text | Free text, up to 2,000 characters |
| Integer | A whole number |
| Number | Any number |
| Boolean | `true` or `false` |
| Select | One of your options |
| Multiselect | Any number of your options |

## Write descriptions that steer Mo

Mo has no other context for a field, so the field and option descriptions are
the prompt. Say what the value means, what to base it on, and how to decide
between close cases:

```text theme={null}
Field: Severity (Select)
Description: How badly the bug affects checkout users.

Options:
  critical: Users cannot complete a purchase.
  high: A core flow fails, but a workaround exists.
  low: Cosmetic issues, copy errors, or layout problems.
```

Concrete criteria give more consistent values than labels alone. Mo picks only
from the options you define, so cover every case you expect.

## Where values appear

* Bugs get values only once Mo reproduces them.
* Values show on bug details in the session, and in the `customFields` object of
  the exported [session report](https://momentic.ai/docs/mo/reports.md).

Start a new session after you change fields. A session that is already running
can keep using the fields it started with.

## Limits

* 50 fields for bug reproductions.
* 100 options per Select or Multiselect field.
* 100 characters per field or option name, 2,000 per description.
* About 32 KB in total, counting field and option names, descriptions, and
  types. Over that, saving fails even if each field is within its own limits;
  shorten names or descriptions, or remove fields or options.


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