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

Install the Momentic GitHub App on the repository, then name it in the brief:
Mo reads any repository the GitHub App can see as read-only context. It does not push code or open pull requests. Two deeper integrations live on top of the App:
  • Workspace repositories. Select repositories on the Mo workspace page and every session starts from a snapshot of them at /home/user/workspace/repos/<repo-id> with read-only Git credentials. The session agent reads the code, runs git log over a window, and maps commits to the flows they touch. This powers diff-based regression.
  • Pull request runs. Mo scopes a session to the change, posts the result as a comment, 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 web application firewall (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 distributed denial of service (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.

​
Drive Mo from a coding agent

mo skills installs the mo-qa skill into the coding agents it detects: Claude Code, Cursor, Codex, Copilot, and OpenCode. After that the agent runs the whole loop in plain language: write the brief, start the session, read the report, fix what it found, and send the recheck. See use the Mo CLI for what runs underneath.

​
Reach a private target

mo tunnel publishes a local or private address to the session sandbox, so Mo tests a branch on your machine or an internal environment. One tunnel holds every address the session needs. See test a local build through a tunnel.

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