> ## Documentation Index > Fetch the complete documentation index at: https://momentic.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file. > For an unattended setup, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell. > You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back. > Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx skills@latest add momentic-ai/skills`. > Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags. > Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators. Physical devices are not supported. # Why Mo, not your coding agent's browser > How a Mo session differs from Devin, Codex, Cursor, or Claude Code driving a browser. Your coding agent can already open a browser. Reach for a Mo session instead when you want a pass over a whole product area rather than a check on the change you just made. ## Coverage in parallel A coding agent verifies in the session you are in: one browser, one flow at a time, while your terminal waits for it. A Mo session gives every test case its own agent and its own browser, simulator, or emulator, so a pass over dozens of flows does not take the sum of their run times. See [parallel agents](/docs/mo#parallel-agents) for the numbers, and [run a session](/docs/mo/sessions) to start one. ## Cover the flows you did not change A coding agent tests what it changed, because that is the context it holds. It does not know which other flows the change can break. Mo starts from a product objective, an uploaded spec, or an open prompt, and the explore agents walk the product area to find the cases, including states that no test covers. You get the case list in the report, so you can see what was covered and add what was missed. See [session reports](/docs/mo/reports) and [use cases](/docs/mo/use-cases). ## What reaches the report An agent that sees a failure once can report only what it saw once, and you are left deciding whether to trust it. In Mo, a suspected bug goes to a bug reproducer agent that starts from a clean session with no state from the agent that found it. Only a bug it reproduces reaches you. A case that access blocks is reported as `blocked` instead of as a bug. See [session reports](/docs/mo/reports). ## What Mo remembers about your product A coding agent session starts with no memory of your product, so you explain the same conventions on the next pass. Momentic keeps a [knowledge base](/docs/ai/knowledge-base) of your terminology, your rules, and your known flows, and the agents retrieve it during a session. Triage adds to it, so a later run does not report the same intended behavior again. See [triage](/docs/mo/triage). ## Next The target, the scope, the accounts, the test data, and the limits. Start a session, read the report, and triage what it found.