Skip to main content
Mo plans its own coverage, so the brief sets the boundary of the session. A brief can also come from a file you upload to the session or a document a connected MCP server can read. Start with one area, read the report, then widen the scope.

Example briefs

Run a plain-text brief with qa start "$(cat brief.md)". The PR example adds --pr and --url, and the local example adds --tunnel; see the qa CLI.

Bug bash a P0 feature area

Check the last 24 hours of diffs

Select workspace repositories so Mo can read the commits.
For a release branch, name the branch and have Mo confirm the checked-out revision. The target deployment must run that revision too.

Run Mo on a pull request

Requires the Momentic GitHub App on the repository. Mo reads the PR’s diff and tests the preview:
See PR sessions.

Test from an existing spec or test plan

Upload the file, then point Mo at the sandbox path qa upload prints:

Test a preview deployment

If the preview sits behind a firewall or a deployment bypass, see bot protection.

Test a local branch

Keep the local URL in the brief; Mo resolves it through the tunnel. See tunneling.

Test a mobile app

Upload an iOS simulator build (.app.zip) or an Android emulator APK, select it in the composer, and give no URL. Device builds (.ipa) won’t run in Mo. Mo installs the build on a remote simulator or emulator. To rerun a brief on a cron, add a schedule. To fix and recheck findings from a coding agent, see run and recheck.