Skip to main content
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 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. See 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:
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 Trigger label under Label trigger in Settings > Run settings (Settings > Triggers in some workspaces) and apply that label to the PR. The person who adds the label must connect GitHub in Settings > Profile. 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. Clear Trigger label to disable label triggers.

From the CLI

From the CLI, start against the PR and its deployment:

Choose a preview

A PR start requires a preview target; an environment supplies configuration but does not replace the preview. Provide its URL or let Mo discover a Vercel, Cloudflare Pages, or Netlify preview link. If discovery is blocked or ambiguous, report the blocker and ask for the preview rather than testing a shared environment. Mo retries pending deployments for up to 10 minutes. See PR API requests and qa start options 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 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 the root agent to mark the task complete, with no bugs, static findings, or unpublished local changes. Mo must also be idle and have no pending questions. Bugs and runtime errors fail the check. Static findings, incomplete work, or unpublished local changes 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 for other connections.