Skip to main content
Start a session from the Mo composer in the Momentic app, or with qa start. Write a brief; Mo asks for anything it still needs before it starts.
Configure the session with session settings: effort, environment, browser, repositories, sign-in, and test data. See effort for testing time and cost.
Two agents in an existing Acme Plant Shop session, with cart and sign-up coverage summaries

View each agent's checks and reported outcome during a session

During the session

Bugs appear in the report while the session runs, often within minutes. Open any sub-agent’s transcript to see what it did. Leaving the page doesn’t stop Mo. Text messages steer active work between tool calls. Attachments and setup changes wait for the next turn. For a browser notification when a session finishes or needs you, turn on Alerts in this browser under Settings > My notifications and set those events to Browser. Alerts show while a Mo tab is open in the background.

Repeat a session on a schedule

Open Schedules in the Mo section of the app. A schedule holds a name, the prompt, a frequency or cron expression, and a time zone. It can pin an Environment, Effort, Interaction speed, Browser, Connector, and Tools for every run and for Run now. Each run starts a new session, listed with its report on the schedule page. With Slack connected, a schedule posts one message per run: the result, or a notice that Mo needs input. Later follow-ups don’t post again. A deleted pinned environment fails the run at start.

Find a session

The Sessions page lists every session in the organization. Filter by platform (Web, Android, iOS) and environment. Filters live in the URL, so you can share a filtered view. Each session’s menu has Rename and Archive. For bugs from every session, open Findings.