Triage a bug - Momentic
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.
From the CLI
List bug names and their current statuses, then use the exact name to record a decision:
qa bugs list <session-id>
qa bugs set-status <session-id> checkout-error accepted
The statuses are open, accepted, works-as-intended, cannot-reproduce, and duplicate. Use open to reset a decision. Both commands print JSON. CLI decisions appear in the dashboard. These commands do not create Linear or Jira issues. works-as-intended saves the decision without creating a knowledge entry; use the dashboard to capture the reason. Changing to another status unlinks any existing knowledge entry from the bug but keeps the entry in the knowledge base.
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:
Explain why the behavior is expected
Type the reason, for example “The confirmation modal is intentional. It prevents accidental deletes.”
Review the suggested entry
Mo drafts a knowledge base entry from your reason and the bug, or matches an entry that already covers it.
Accept or reject it
Accept, and Mo saves the entry and links it to the bug. Reject it, or choose Skip knowledge, and Mo still marks the bug as intended and writes no entry.
Later sessions can retrieve the entry as guidance when investigating the same behavior. Review the entry’s scope so it applies to the intended environment and flows. Momentic test agents can also use the knowledge base. 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 a Momentic test, so the next release checks it without a Mo session. For the fix itself, qa report exports report data and available recordings into a directory your coding agent reads, and qa send asks Mo to rerun the original reproduction after the patch lands. See fix what it found, then recheck. To keep the flow covered, the case in the report already has the preconditions, the outline, and the acceptance criteria a test needs. Give the case to your coding agent with the Momentic MCP server and the momentic-test skill for web or momentic-mobile-test for mobile. The agent writes the .test.yaml file in your repository:
/momentic-test write a test for the case "<case title>" from the Mo report
Run it with npx momentic run or npx momentic-mobile run, then add it to the suite your CI runs. See run tests locally.