> ## 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, first check whether Claude Code already has the Momentic plugin. With the plugin, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools none` and ignore any CLI skills-install suggestion in its output. Otherwise, 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. > Mo is the AI QA engineer, separate from repository YAML tests. With the Momentic plugin, use bundled mo-qa and hosted OAuth by default. Without the plugin, install only mo-qa with `npx -y qa skills --target `. Keep the requested interface. Otherwise, use hosted tools for web or mobile, including private web targets with an existing Connector. Run sessions that need a new tunnel with the qa CLI. If you can't run commands on the machine that reaches the target, ask the user to start the tunnel there, then use hosted tools unless you lack them or the CLI was requested. For a requested hosted session, use an online Connector and pass its name as access, not a CLI tunnel ID. If none is online, ask the user to run `npx -y qa tunnel start --name
` on a machine that reaches the target and wait. Do not run login or tunnel commands for them. For a requested hosted session, report unavailable tools or authentication failures without starting a CLI session. For coding-agent bridge setup, ask the user to complete `npx -y qa login`, then add momentic-hosted as a stdio server running `npx -y qa mcp`. Plugin users must explicitly opt in and disable their hosted plugin entry before adding the bridge. Claude.ai/ChatGPT connectors keep https://mcp.momentic.ai with OAuth. After hosted testing completes, read the report and summarize findings and uncovered requirements. Call `momentic_mo_stop_session` only when the user asks or agrees. For CLI sessions, unless the user wants more testing, export the report, run `qa stop --subagents` even if export fails, then summarize. The CLI is qa, not mo. Docs: https://momentic.ai/docs/mo/quickstart.md. > Ask the user to complete browser sign-in. For local CLI tools, use the exact MOMENTIC_API_KEY environment variable. If it is absent, ask the user to create a key at https://app.momentic.ai/settings/api-keys and set it in the agent's environment. Never print the key or ask the user to paste it into chat. > Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Claude Code users with the Momentic plugin should use its bundled skills and skip CLI skills installation. Otherwise, run `npx momentic skills -y --target ` or `npx momentic-mobile skills -y --target `. Both install momentic-test, momentic-maintain, and momentic-spec with web/mobile references. Use the running agent's target. The Momentic plugin also includes mo-qa; qa skills installs only mo-qa. > 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. # Linear and Jira > Read Linear and Jira issues during a Mo session and file bugs back to them. Mo reads Linear and Jira issues to scope a session, and you file confirmed bugs back from the finding. ## Linear Use Linear issues and acceptance criteria to scope Mo sessions. File a finding back to Linear with **Create Linear issue** on the bug. ### Read issues during testing Add [Linear MCP](https://linear.app/docs/mcp) through the [MCP connection setup](https://momentic.ai/docs/mo/integrations/mcp.md#connect-a-server). Use these settings: | Setting | Value | | - | - | | Server URL | `https://mcp.linear.app/mcp` | | Authentication | **OAuth** | For context without write tools, use `https://mcp.linear.app/mcp/readonly`. Linear also accepts an API key or OAuth token through an `Authorization: Bearer ` header. Review the connected account's permissions and the tools listed by **Test connection**. Include the issue ID and app URL in your brief: ```text theme={null} Read Linear issue SHOP-412 and its linked Notion specification. Test the acceptance criteria on https://preview.example.com. Do not edit the issue or specification, submit payment, or place an order. ``` Connect [Notion](https://momentic.ai/docs/mo/integrations/mcp.md#notion) too if the brief needs a linked specification there. Specify whether Mo may create or update issues in your brief. ### File bugs Connect **Linear** in **Settings > Integrations**. In a Mo session's bug report, open **Create issue** and choose **Create Linear issue**. Pick the team and edit the prefilled title and description before you create it. With **Atlassian** connected there, **Create Jira issue** files it in Jira. Filing is per bug: **Accept** only marks the bug accepted. **Create issue** also offers **Create GitHub issue**, which needs the Momentic GitHub App with **Issues: write**. See [triage](https://momentic.ai/docs/mo/triage.md). ## Jira Give Mo Jira acceptance criteria and Confluence specifications through Atlassian Rovo MCP. Your connected account's permissions determine which pages, issues, and tools Mo can access. ### Connect Jira and Confluence Add [Atlassian Rovo MCP](https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/) through the [MCP connection setup](https://momentic.ai/docs/mo/integrations/mcp.md#connect-a-server): | Setting | Value | | - | - | | Server URL | `https://mcp.atlassian.com/v2/mcp` | | Authentication | **OAuth** | Sign in and grant access. ### Test from an issue Include the issue or document reference and your app's URL in your brief: ```text theme={null} Read Jira issue SHOP-412 and its linked Confluence specification. Test the acceptance criteria on https://preview.example.com. Do not edit Jira or Confluence, place an order, or submit payment. ``` Review the [provider's account requirements and permissions](https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/). Specify whether Mo may use tools that write data. The native **Atlassian** connection in **Settings > Integrations** files issues from repository test results and Mo bugs. Connect Rovo MCP to let Mo read Jira and Confluence during a session. If you can't connect it, attach an exported spec or [upload one](https://momentic.ai/docs/mo/cli.md#move-files) and include its sandbox path. ### Xray To sync test cases or import execution results into Xray, [contact support](https://momentic.ai/docs/account/help.md) with the task, your Jira deployment type, and the report format you need. These tasks need different connections and configuration. Repository tests can export [JUnit XML](https://momentic.ai/docs/guides/reporting.md#custom-outputs-and-junit-reports) or [JSON](https://momentic.ai/docs/guides/reporting.md#export-run-results-as-json) for a separate import step. These reporters write result files; they don't create Jira issues or sync Xray test cases. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.