Skip to main content
Start a bug bash against your app, then review the coverage and findings. Mo needs no test files or repository code.

Setup with coding agent

Paste this prompt into your coding agent from your project directory. It installs the Mo CLI and skill, connects hosted tools, and asks what to test.
Setup prompt

Prerequisites

Get Mo access and a reachable web URL or an uploaded mobile build. Authenticated flows need a test account and sign-in instructions. For private apps, connect a tunnel. For deployment protection or firewalls, allow Mo’s browser. Mobile sessions need Mo mobile access and an uploaded iOS simulator .app.zip or Android APK. Device builds (.ipa) don’t run in Mo.
1

Open Mo

Open Mo in the Momentic app. Choose Web and put the exact URL, including the path, in your brief. For mobile, choose iOS or Android and an uploaded build instead.Start with one flow you can review, such as a cart or sign-in form. Use an account with access to that flow. Tell Mo which account state to start from and which data it can change.
2

Describe one area to test

Name the expected behavior and prohibited actions. Replace this URL with your target:
Provide test credentials through a workspace environment. Choose an effort and send the brief with Send message.
3

Follow the session

Answer access or test-data questions in the chat. Open a sub-agent’s transcript to see what it checked. Text messages steer active work; attachments and setup changes wait for the next turn.You can leave the page while Mo works. Return to the session to answer questions or change the scope. If Mo can’t reach the app, resolve access before asking it to continue testing.
4

Review coverage and bugs

Compare the report with your brief. Check verified, issues found, and blocked verdicts, then read each bug’s reproduction steps and available recording. No bugs doesn’t mean every requested flow was tested. Resolve blockers and ask Mo to check missing flows.Triage findings: accept bugs or dismiss intended behavior. After deploying a fix, ask Mo to recheck it.Keep the finding’s expected and actual behavior with its reproduction steps when you share it with an engineer. Use the report to distinguish bugs from flows Mo couldn’t finish.
Mo finding for the Acme Plant Shop demo, showing expected and actual cart totals and four reproduction steps

Review expected behavior, actual behavior, and reproduction steps

Next