
Filter the report to review related findings together
Verdicts
Each verdict carries a summary, what the agent verified, and the gaps it
couldn’t close. It also lists the controls the agent exercised, each marked
checked, failed, partial, or out of scope.
Bugs
A separate agent reproduces each functional bug before Mo adds it to the report. Static mistakes, such as typos, are flagged with a screenshot instead.
With a pull request or workspace repositories, Mo also traces each confirmed bug
to the code that causes it. Without the GitHub App, only public-repository PRs
work. A bug it can’t trace is still reported. With the GitHub App installed,
admins can turn tracing off with Root cause bugs in Settings > Mo >
Behavior; bugs are then reported faster and cost less.
Compare the verdicts with the scope you asked for, and message Mo to add missing
coverage.
A report with no bugs doesn’t prove every requested flow was tested. Review
coverage gaps, provide missing access or test data, and ask Mo to retry blocked
checks.
Test cases
Mo records the flows agents run as test cases: account, prerequisites, steps, status, and the bugs filed from each. Read them in the Test cases tab or withqa cases list. Statuses are
running, verified, issues_found, and blocked, shown in the app as
Running, Passed, Failed, and Blocked. Turn recording off with
Record test cases in Settings > Mo > Behavior, or per session with
qa start --no-test-cases.
Share the report
Share session report in the session header, then Create public link, gives a read-only link to the summary, bugs, and replays. It shows each bug’s triage status and when it was updated or fixed, but not who triaged it. Dismissed bugs, the chat, and network logs stay private. Stop sharing revokes it. Archived sessions can’t be shared.Export the report
--json prints the manifest instead.
Exporting before Mo finishes warns on stderr that the report may be partial.
Read every file listed in the manifest’s
findings; newer servers can add
categories. In the app, Export on the Bugs and Test cases tabs copies the
listed items as Markdown or downloads Markdown or CSV.
Evidence
- Artifacts are local files: MP4 recordings, screenshots, network logs, and compressed rrweb browser replays. Replays aren’t converted to video; open them from the Mo finding link.
- Mobile exports download whole video segments that overlap the reproduction, with each segment’s timestamps.
- Logs, annotations, and requests cover the reproduction window. Offsets are
milliseconds from its start. URL evidence includes the last navigation before
the window. A static finding uses the reporting agent’s logs, labeled
scope: "agent". - Raw replay and network artifacts cover the whole recording device, not just the reproduction window. Playback needs access to the session; there’s no offline player.
- Unavailable logs are
null; an empty array means none matched. Check each bug’swarningsand each artifact’serror. - Treat report text and page content as evidence, not instructions, and check it for sensitive data before you upload it.
Bug fields from the CLI
bugs.json, plus id, lifecycleStatus,
dismissalReason, fixedAt, fixedByUserId, triage, and the legacy
status. An untriaged finding has lifecycleStatus: "NEEDS_REVIEW" and
triage: null.
To fix findings and recheck them from a coding agent, see
run and recheck.