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

# How teams use Momentic

> Starting points for local feedback loops, bug bashes, PR checks, web and mobile coverage, migration, and coding agents.

Momentic fits wherever you test: locally, in PR previews, on staging, and in CI.
Start with the work your team needs to verify, then follow a reading path below.

## Developers testing changes locally

Bug bash your branch's local dev server with Mo while you code, then test the PR
or its preview deployment. Run regression tests locally before pushing, and turn
a Mo finding into a test that checks the fix.

1. [Give Mo access to your local dev server](https://momentic.ai/docs/mo/tunneling.md)
2. [Run Mo from your coding agent or terminal](https://momentic.ai/docs/mo/cli.md)
3. [Test a PR or preview deployment with Mo](https://momentic.ai/docs/integrations/github.md#start-a-pr-session)
4. [Run regression tests locally before pushing](https://momentic.ai/docs/running-tests/running-locally.md)
5. [Turn a Mo finding into a regression test](https://momentic.ai/docs/mo/regression-tests.md)

## QA leads running bug bashes

Give Mo a target and a brief before a release. Review its findings, triage the
bugs, and turn the ones you need to catch again into regression tests.

1. [Start your first Mo session](https://momentic.ai/docs/mo/quickstart.md)
2. [Write a brief](https://momentic.ai/docs/mo/brief.md)
3. [Triage findings](https://momentic.ai/docs/mo/triage.md)
4. [Turn a bug into a regression test](https://momentic.ai/docs/mo/regression-tests.md)

## Engineers checking pull requests

Use Mo to explore a PR's preview deployment. Keep tests for critical flows in
your repository and run them in CI on each change.

1. [Test a PR with Mo](https://momentic.ai/docs/integrations/github.md#start-a-pr-session)
2. [Write your first web test](https://momentic.ai/docs/quickstart/web.md)
3. [Run tests in GitHub Actions](https://momentic.ai/docs/running-tests/ci/github-actions.md)
4. [Choose a CI setup](https://momentic.ai/docs/guides/common-setups.md)

## Web teams

Start with your web app's URL and a supported browser. Write tests for critical
flows, then run them in CI on each change.

1. [Set up web tests](https://momentic.ai/docs/quickstart/web.md)
2. [Choose a browser](https://momentic.ai/docs/platforms/web/browsers.md)
3. [Write test steps](https://momentic.ai/docs/core-concepts/steps.md)
4. [Run tests in GitHub Actions](https://momentic.ai/docs/running-tests/ci/github-actions.md)

## Mobile teams

Start with your iOS build or Android APK and a simulator or emulator. Write
tests for the flows you need to check across releases, then inspect run results
when a test fails.

1. [Set up iOS tests](https://momentic.ai/docs/quickstart/ios.md)
2. [Set up Android tests](https://momentic.ai/docs/quickstart/android.md)
3. [Run tests locally](https://momentic.ai/docs/running-tests/running-locally.md)
4. [Read test results](https://momentic.ai/docs/running-tests/results.md)

## Teams migrating existing tests

Move a small set of critical flows before converting a full suite. Use the
migration guide for your current framework, then organize shared behavior into
modules.

1. [Migrate from Playwright](https://momentic.ai/docs/guides/migrate/from-playwright.md)
2. [Migrate from Cypress](https://momentic.ai/docs/guides/migrate/from-cypress.md)
3. [Organize your tests](https://momentic.ai/docs/best-practices/test-organization.md)
4. [Reuse steps with modules](https://momentic.ai/docs/core-concepts/modules.md)

## Coding-agent-first teams

Install the Momentic plugin to give your coding agent skills and MCP
connections. Use the hosted server for Mo sessions and run history, and local
servers to inspect your app while writing and repairing tests.

1. [Install the Momentic plugin](https://momentic.ai/docs/coding-agents/skills.md#mo)
2. [Use the hosted MCP server](https://momentic.ai/docs/mo/chatgpt-and-claude.md)
3. [Set up standalone local MCP servers](https://momentic.ai/docs/coding-agents/mcp-server.md)
4. [Build with AI](https://momentic.ai/docs/coding-agents/building-with-ai.md)
5. [Maintain tests](https://momentic.ai/docs/reliability/auto-maintenance.md)


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