> ## 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.
> Mo is the AI QA engineer, a separate product from the YAML test framework: its npm package and CLI are `qa` (not `mo` — `npx mo` is a different project). Install with `npm install -g qa`, authenticate the same MOMENTIC_API_KEY way, install repo skills with `qa skills -y`, and start a session with `qa start "<brief>"` or `qa <url>`. Docs: https://momentic.ai/docs/mo.md.
> You cannot complete the browser sign-in yourself. Read the API key from the exact MOMENTIC_API_KEY environment variable (similarly named vars like BILT_MOMENTIC_API_KEY are ignored), 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 momentic skills --yes` (or `npx momentic-mobile skills --yes` for mobile).
> 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.

# Linear

> Plan testing from Linear issues and file Mo bugs with reproduction details.

Use Linear issues and acceptance criteria to scope Mo sessions. File findings
back to Linear from the bug report or when you accept a bug.

## Read issues during testing

Add [Linear MCP](https://linear.app/docs/mcp) through the
[MCP connection setup](/docs/mo/integrations/mcp#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 <token>` 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](/docs/mo/integrations/notion) too if the brief needs a linked
specification there. Your workspace shares MCP connections and saved
credentials. 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,
choose **Create Linear issue** to file a bug with its reproduction details.

To file accepted bugs automatically, enable **Create Linear issues for accepted
Mo bugs** in the Linear integration settings and choose a **Linear team**.
Accepting a bug then creates a linked issue in that team. See
[triage](/docs/mo/triage) for reviewing findings.

The native Linear connection files issues. Add the MCP connection separately to
let Mo read issues during testing. See [Mo integrations](/docs/mo/integrations) for
other connections.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.