Skip to main content
Connect the services Mo needs for a brief or a target.

Provide the brief

You can give Mo:
  • A plain prompt.
  • An uploaded file.
  • A Confluence page URL or page ID after you connect Atlassian in Momentic settings > Integrations.
See write a good brief for what a brief must contain.

Use GitHub context

Connect a repository, then pass its owner and name:
Mo uses the connected repository as read-only context. It does not push code or open pull requests. Install the Momentic GitHub App on the repository to run Mo on a pull request. Mo scopes the session to the change, comments the result on the pull request, and reports a status check you can require before a merge. A comment on the pull request also starts a scoped run. See run Mo on a pull request.

Test a protected target

Mo reads its own browser traffic and detects the hosting platform and the protection type. Supported hosting platforms:
  • Vercel
  • Cloudflare
  • Google
  • Netlify
  • CloudFront
  • Fastly
  • Akamai
Supported protection types:
  • Vercel deployment protection
  • Vercel firewall challenge
  • Cloudflare challenge
  • Cloudflare Turnstile
  • reCAPTCHA
  • hCaptcha
  • Device fingerprinting
  • HTTP basic auth
With Vercel connected in Momentic, Mo applies the deployment-protection bypass for a connected project. With Cloudflare connected, it applies the WAF skip for a zone the account owns. If nothing connected serves the host, Mo reports the host instead of retrying. Vercel attack mode and DDoS mitigation still need a WAF rule from the project owner, and Mo cannot solve a Turnstile, reCAPTCHA, or hCaptcha widget. Mo reports the host, and you connect the provider or disable the widget on the test environment.

Use test management

Connect TestRail, Qase, or Testiny in settings > Integrations. Mo’s test cases carry the fields those tools use, so a case reads the same in Momentic and in the connected project. Mo syncs its cases and reports the result of each run.

Use issue trackers

Connect Jira or Linear in settings > Integrations. File an accepted bug as an issue from the report. The issue carries the expected and actual behavior, the reproduction steps, and a link back to the session. See session reports for the fields Mo records for each case and bug.