> ## 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. > Mo is the AI QA engineer, a separate product from the YAML test framework: its npm package and CLI are `qa` (not `mo` — `npx mo` is a different project). Install with `npm install -g qa`, authenticate the same MOMENTIC_API_KEY way, install repo skills with `qa skills -y`, and start a session with `qa start ""` or `qa `. Docs: https://momentic.ai/docs/mo.md. > You cannot complete the browser sign-in yourself. Read the API key from the exact MOMENTIC_API_KEY environment variable (similarly named vars like BILT_MOMENTIC_API_KEY are ignored), 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 momentic skills --yes` (or `npx momentic-mobile skills --yes` for mobile). > 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. # GitHub > Use repository context, start PR sessions, and review Mo reports and checks in GitHub. Connect GitHub to give Mo repository context, start pull request (PR) sessions from the web composer, comments, labels, or the CLI, and receive reports and commit checks. Reports include findings and playback links for selected verified flows when recordings are available. ## Connect GitHub Install the [Momentic GitHub App](/docs/integrations/github#install) in **Settings > Integrations**. Connect your personal GitHub account in **Settings > Profile** to start sessions through comments or labels. You must belong to exactly one Momentic workspace connected to that installation; otherwise, start in the intended workspace. Workspace access and billing limits apply. ## Add repository context Select repositories on the **Mo workspace** page for read-only code and diffs. Include a repository or PR reference and the running app URL in your [brief](/docs/mo/brief). See [workspace repositories](/docs/mo/sessions#workspace-repositories) for refresh behavior and revision checks. ## Start a PR session ### From the web app Paste a GitHub PR link into your description, or select **+ > Pull request** and enter its URL. The selected PR appears as a GitHub pill; remove it with the **X**. Include the app URL in your description when known, or select an environment. ### From a comment Mention Mo in a new comment on an open PR: ```text theme={null} @momentic-ai please test checkout on https://preview.example.com. Check discounts and failed payments. Do not submit an order. ``` Mo acknowledges the request with an eyes reaction and posts a session link when testing starts. Open that link to answer access and testing questions. Questions, incidental mentions, edits, and inline review comments don't trigger sessions. ### From a label Set **Mo trigger label** in **Settings > Integrations > GitHub** and apply that label to the PR. Mo tests the captured commit, skipping changes without testable app behavior. Remove and reapply the label for another run; removing it or pushing commits doesn't cancel or restart testing. Leave the setting blank to disable label triggers. ### From the CLI From the CLI, start against the PR and its deployment: ```bash theme={null} qa start --pr https://github.com/acme/shop/pull/412 --url https://preview.example.com ``` ### Choose a preview An environment supplies the target without requiring a preview URL. Otherwise, Mo looks for Vercel, Cloudflare Pages, or Netlify preview links. If discovery fails or finds multiple targets, the session still starts: Mo can inspect the PR or ask you which app to test. Mo retries pending deployments for up to 10 minutes. See [PR API requests](/docs/mo/integrations/scripts-and-ci#start-a-pr-session) and [`qa start` options](/docs/cli-reference/mo/commands/start) for unpublished patches. ## Review results PR sessions show a **PR** badge. Each session updates its review with findings, agent counts, runtime, and up to three verified-flow recordings. Earlier reviews collapse as **Outdated**. **Copy for your coding agent** includes bug summaries and available source diagnoses. Open the [report](/docs/mo/reports) for evidence. ### Commit checks With Checks access, the **Mo** check follows the latest request on that commit. It stays pending during testing or questions. Passing requires verified cases without bugs or coverage gaps. Bugs and runtime errors fail; static findings or incomplete coverage can produce a neutral result. The check doesn't verify the deployed revision. With **Pull requests: write**, Mo posts reviews; with **Issues: write** alone, it posts PR comments. See [Mo integrations](/docs/mo/integrations) for other connections. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.