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

# Review and triage bugs

> Read a scan's bugs on the Bugs page, open the evidence for each one, mark bugs fixed or dismissed, and copy a bug as Markdown for your coding agent.

Every completed scan's bugs appear on the **Bugs** page. Click **Bugs** in the sidebar under **Runs**.

![The Bugs page for the Storefront project: scan #4 selected, 7 open, 1 fixed and 1 dismissed, and the bug table grouped by type](https://mintcdn.com/peeps-ai/e5SiOQ2AD7q-J5yy/images/bug-scan/bugs-page.png?fit=max\&auto=format\&n=e5SiOQ2AD7q-J5yy\&q=85\&s=0107e3eb1bd87dea42761b36a1d442d8)

## Read the page

The header shows when the scan you're viewing ran, how many pages it visited, and how many bugs it found.

* **Scan** picks which scan to view. Each completed scan is listed with its number, when it finished, its bug count, and its page count. The latest one is selected. While a new scan runs, the page keeps showing the previous results.
* **Open**, **Fixed** and **Dismissed** count the scan's bugs by status.
* The table lists the bugs, grouped by type.

Each bug's row shows:

| Column | What it shows |
| - | - |
| **Type** | The kind of bug, such as **Broken link** or **Accessibility**. See [what a scan checks](https://docs.peepsai.com/bug-scan/overview.md#what-a-scan-checks). |
| **Severity** | **critical**, **high**, **medium** or **low**. |
| **Bug** | A one-line title. |
| **Page** | The URL where the agent found it. |
| **Evidence** | A camera icon when there's a screenshot, and a video icon when the bug is marked in the scan's recording. |
| **Status** | **open**, **fixed** or **dismissed**. |

### Group, search and filter

* **Group** groups the table by type, severity or status. Choose **No grouping** for a single list sorted by severity, most severe first.
* **Search** finds bugs by title or page URL.
* **Filter** narrows the table by type, severity or status.

## Open a bug

Click a bug's row to open its details.

![The details panel for a spelling bug, showing its severity and status, the Mark as fixed and Dismiss buttons, a screenshot with the misspelled text outlined, the page URL, a description, the evidence text and the CSS selector](https://mintcdn.com/peeps-ai/e5SiOQ2AD7q-J5yy/images/bug-scan/bug-details.png?fit=max\&auto=format\&n=e5SiOQ2AD7q-J5yy\&q=85\&s=0cc2b4455f18a8ce11bab6d7a55cb852)

The panel shows whatever evidence the agent collected for the bug:

* **Recording.** The scan's video, starting at the moment the agent found the bug. **Bug detected at** gives that time.
* **Screenshot.** The page with the problem in view. Visible bugs, such as spelling, accessibility and visual issues, usually have one. Console, API, slow-page and broken-link bugs don't.
* **Page.** The URL where the bug is. Click it to open the page.
* **Description.** What's wrong, in the agent's words.
* **Evidence.** The exact text, error or response behind the bug.
* **Selector.** A CSS selector for the element involved.
* **Console messages** and **Network errors.** The raw browser console entries or failed requests, for console and API bugs.

## Triage a bug

An open bug's panel has two buttons. Both need the **Contributor** role or above.

* **Mark as fixed.** You've fixed the bug.
* **Dismiss.** The bug isn't worth fixing, or isn't a bug.

The change can't be undone from the app, and it applies only to this scan's copy of the bug.

> [!NOTE]
>
> Each scan reports bugs on its own. Peeps doesn't match bugs between scans, so a bug you haven't fixed shows up again, as **open**, in the next scan. Marking a bug fixed doesn't hide it from future scans. To check a fix, run a new scan and look for the bug in it.

## Hand a bug to your coding agent

Click **Copy** on a bug's row to copy it as Markdown, ready to paste into Claude Code, Cursor, or another coding agent. The button then reads **Copied**, so your team can see which bugs someone has already picked up.

The Markdown has the bug's details and evidence. Sections without content are left out:

````markdown theme={null}
## Bug: "Recieve" should be "Receive"

- **Type:** Spelling
- **Severity:** medium
- **Status:** open
- **Page:** https://staging.acme-shop.com/account/orders

### Description
The empty state on the order history page reads "You will recieve an email when your order ships." "Recieve" is misspelled; it should be "receive".

### Evidence
```
You will recieve an email when your order ships.
```

### Selector
```css
main .orders-empty > p
```
````

Console and API bugs also get **Console errors** and **Network errors** sections, with the raw data as JSON. Screenshots and recordings aren't included, so open the bug in Peeps to see them.


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