> ## 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.

# Triage a bug

> Accept a bug, mark it as a duplicate, or capture it as intended behavior in the knowledge base so later runs do not report it again.

Every bug in a Mo report starts untriaged. Your decision is recorded on the bug,
with who made it and when, so the next reader sees it.

## The decisions

| Decision              | Use it when                                                                       |
| --------------------- | --------------------------------------------------------------------------------- |
| **Accept**            | The behavior is a defect, and it must be fixed.                                   |
| **Works as intended** | The behavior is correct, and Mo did not know that yet.                            |
| **Can't reproduce**   | You followed the steps and the behavior did not appear for you.                   |
| **Mark as duplicate** | Another bug in the report, or an issue you already track, covers the same defect. |

**Reset** clears a decision and returns the bug to untriaged.

## Works as intended

Mo reports an intended behavior again on the next run unless the run knows about
it, so a works-as-intended decision records the reason:

<Steps>
  <Step title="Explain why the behavior is expected">
    Type the reason, for example "The confirmation modal is intentional. It
    prevents accidental deletes."
  </Step>

  <Step title="Review the suggested entry">
    Mo drafts a [knowledge base](/docs/ai/knowledge-base) entry from your reason and
    the bug, or matches an entry that already covers it.
  </Step>

  <Step title="Accept or reject it">
    Accept and the entry is saved and linked to the bug. Reject it, or choose
    **Skip knowledge**, and the bug is still marked as intended with no entry
    written.
  </Step>
</Steps>

Momentic retrieves the relevant knowledge entries on every AI-assisted step, so
a later Mo session reads the entry while it explores that flow and does not
report the behavior again. Your Momentic tests use the same entries.

The linked entry stays visible on the bug. If you change the decision later, Mo
asks whether to unlink the entry as well.

## What to do with an accepted bug

Fix it, then keep the flow covered by writing the case as a Momentic test.