mo-qa

Run QA with Mo

Mo is Momentic's autonomous QA engineer. It runs in a hosted sandbox, where it can test web applications with a browser, inspect network traffic, run code and shell commands, delegate exploration, and report test cases and product bugs. Treat its filesystem and environment as remote, not as the user's machine.

When the user asks to fix bugs found by QA, also read Repair loop and continue through diagnosis, repair, and verification. Otherwise, run QA without changing application code.

Setup

Run mo version. If it fails or recommends an update, read Installation.

Assume authentication is already configured. If an operational command reports an authentication error, read Authentication.

Use the target implied by the conversation. If it is unclear, ask the user what to test. For a local or private target, read Tunneling and retain its tunnel_id. For a public target, use its exact URL.

Write the QA brief

Treat the brief as the whole input. State:

1. Target URL: Include the exact path and query the change affects.
2. Expected behavior: Explain what changed and what it should now do in product terms.
3. Sign-in instructions: Name the login method and test account to use.
4. Test data rules: State what Mo may create and what it must not touch.
5. Out-of-bounds actions: Call out deletions, payments, emails, production data, bulk operations, and any other destructive action. Mo may take destructive actions if the brief invites them.
6. Acceptance criteria: List the checks that decide pass or fail.

Use the user request, task specification, and repository context to fill in the brief. State reasonable assumptions; ask when missing information materially changes the scope or requires credentials or permissions you don't have.

Run a session

Write the brief before invoking the CLI, then pass it as one quoted argument:

brief=$(cat <<'EOF'
Target URL: https://preview.example.com/checkout?variant=express
Expected behavior: Express checkout now keeps the selected shipping method when the customer returns from payment.

Starting returns before Mo finishes. Preserve both values: every later command needs session_id, and the user can watch or join through web_url.

Use start settings only when needed:

• --tunnel "$tunnel_id" connects the session to a configured tunnel.
• --momentic-mode uses smarter Momentic browser tools; omit it for faster Playwright MCP.
• --max-concurrency <count> caps concurrent sub-agents. Omit it by default; pass it only when the user specifies a limit before the session starts.

These settings are chosen when the session starts.

Concurrency cannot be changed on an existing session. A lower value reduces parallel model and browser load, which can help when Mo hits provider rate limits or overwhelms a local target server. If either happens, stop the current session and start a fresh one with a lower --max-concurrency; do not try to repair the affected chat by sending a lower limit after it has started.

Follow the turn reliably

Poll the active session with status for its state, web URL, and bug and test-case counts:

Use --full when you need the latest message or finding summaries. Before summarizing QA results or investigating a bug, read Reports to download and inspect the detailed findings and reproduction videos. Before reporting a bug, check whether the product or the brief's expected behavior is stale.

Use read when waiting for output or retrieving the transcript and pending input. Prefer bounded 30-60 second reads so the caller stays responsive:

Use --from start for reliable polling. It replays the visible transcript, so deduplicate messages when automating. Repeat until the expected assistant reply appears and state is idle, waitingOnUser, or stopped. A timedOut: true response means Mo is still working. If pendingInput is present, answer it with send.

Do not rely on --from latest after start or send: it only captures output produced after the read begins, so a fast turn can finish and return no messages. A timeout accepts 0, milliseconds, seconds, or minutes such as 500ms, 45s, or 4m, up to 290s.

status.state is the shared UI status. ready or sleeping means no agents are running; needs_you means input is needed. read.state describes the visible turn, which can finish while sub-agents are still working. Use status and report --require-idle before consuming a completed QA report.

Continue, stop, or archive

For a follow-up or answer, prefer --wait so the next attention boundary is returned directly:

If Mo is working, send stops the active turn, interrupts in-flight tool work, and starts a new turn from saved history. It does not steer the live turn. Send only when that interruption is intended. Without --wait, success only means the message was accepted; confirm a new assistant reply with read.

Stop only the active turn:

Allow a few seconds for propagation, then verify with read --from start --timeout 0 --json that the state is stopped. Stopping does not delete the session, and already-running sub-agents may finish independently. Pass --subagents to stop running or concurrency-queued sub-agents too without closing their conversations.

Archive a finished session when it should leave the active list:

Archive stops active work. Further send calls are rejected until the session is unarchived in the web UI; the CLI has no unarchive command.

Transfer files

upload needs an existing session and prints the authoritative sandbox path. Send that returned path to Mo; a local path is meaningless inside its hosted machine.

If --output names a directory, create it first. A nonexistent output path is treated as a target filename. Without --output, downloads use MOMENTIC_ARTIFACTS_DIR, then <current-directory>/.momentic-artifacts.

Command reference

Run mo <command> --help for exact options. Global --log-level accepts debug, info, warn, or error.