Skip to main content
Export the session report to a local directory, with one file per findings category, per-bug JSON and Markdown, and available evidence. Give the directory to a coding agent to investigate or fix the reported bugs.

Arguments

string
required
The session to export.

Options

string
Directory to write the report and evidence to. Defaults to MOMENTIC_ARTIFACTS_DIR/mo-report-<session-id> when that variable is set, or .momentic-artifacts/mo-report-<session-id> otherwise.

Output

The command prints the output directory. Add --json to print one JSON object with the absolute outputDirectory and all fields from report.json. Warnings go to stderr in either mode. Inside the directory, report.json is the manifest:
summary.status records the session’s status at export, and summary.completed the root agent’s explicit completion flag. Both, like webUrl, createdAt, lastActivityAt, and latestTurn, are absent when the server does not provide them. When Mo is not done, the command still exports, warns on stderr that the report may be partial, and lists the warning in warnings. For a stopped (cancelled) session, the warning says the report covers Mo’s work up to the stop. Read every file findings names; newer servers can add categories. artifacts holds each download’s bugId, bugName, kind (video, screenshot, replay, network, or mobile), source, and either a local path or an error. Available artifacts include screenshots, MP4 videos, raw compressed rrweb replays and network logs, and mobile recording metadata and overlapping video segments. A browser replay is not an MP4 video. Follow each bugs entry’s details path to its detail file:
bug (shortened here) has the full shape of qa bugs describe and the entries in bugs.json. bugUrl opens the finding in Mo. scope is agent when a static finding uses the reporting agent’s logs, which cover the whole device. Times are epoch milliseconds and offsetMs counts from the reproduction start. consoleLogs entries can carry a trace, annotations carry kind-specific fields, and networkLogs holds HAR entries. A null log list means it was not captured; an empty array means nothing matched. artifacts uses the report.json artifact shape. The issue path contains a Markdown draft for an issue tracker; filing is not required to fix the bug. See report evidence for evidence scope and playback limits. Each verdicts.json entry has status (verified, issues_found, or blocked), summary, verified and gaps string arrays, agent, conversationId, createdAt, and updatedAt. triage.json entries have the triage shape from qa bugs list.

Examples

Export once the session finishes:
List every bug name:

Notes

Exporting does not rerun anything. To compare a recheck, qa send the recheck request, wait for idle, and export again into a second --output directory.