> ## Documentation Index
> Fetch the complete documentation index at: https://www.minitap.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How Mini learns from your feedback

> What happens when you mark a result as not a bug, where Mini keeps what it learned, and how to see what changed.

Every time you tell Mini a result was wrong, it learns from it. The goal is simple: the same false alarm shouldn't come back on the next run.

## Telling Mini it got something wrong

On an issue, click **Not a bug** and explain why in a sentence or two. Mini may suggest a few answers to save you typing. Write it the way you'd explain it to a new tester:

```text theme={null}
The banner is supposed to stop after the last slide. That's the new design.
```

The issue is cleared right away. See [Issues](/docs/minitest/triage/issues.md) for the other triage actions.

## What Mini does with your note

Mini reads your note and keeps what applies where it belongs:

* **For the whole app.** A rule about how your app works, like "prices include VAT" or "the banner stops after the last slide", goes into [Mini's memory](/docs/minitest/get-started/how-mini-tests.md#what-mini-knows-before-it-starts). Every scenario benefits from it.
* **For this scenario.** Something only true for this scenario is kept with it, and Mini reads it the next time it runs that scenario.
* **For the criterion.** If the criterion itself was worded in a way that led to the wrong verdict, Mini rewrites it to say what you meant. The previous wording stays in the history.

Your note is context for the next run, not an automatic pass. Mini still judges the criterion from what it sees on the device.

## Where to see what Mini learned

* **Memory page.** Under your app's settings, **Memory** shows what Mini reads before every run, including the rules it learned from your reviews. You can edit it.
* **Criteria history.** Open a scenario, then **… → Criteria history** to see every version of its criteria and where each change came from: your edits, Mini's suggestions you accepted, or changes Mini made from your feedback. You can revert to an earlier version.

## Feedback inside a draft

When a draft check fails and you think Mini is wrong, click **Not a bug?** and tell Mini what it got wrong. Mini fixes the scenario and checks it again. See [Working with Mini](/docs/minitest/get-started/working-with-mini.md#drafts-change-check-merge).


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