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

# Detail dashboard: review, triage, and resolve bugs

> Review AI-detected findings, triage bugs by status, track code health metrics, and trigger on-demand scans — all from one central workspace.

The Detail dashboard at [app.detail.dev](https://app.detail.dev) is your central workspace for reviewing AI-detected findings, tracking bug status, and managing your repositories. Every scan result lands here first, giving you a single place to decide what gets fixed, dismissed, or escalated.

## Reviewing findings

When Detail finishes scanning a repository, all detected bugs appear in a ranked list. Each row shows:

* **Title** — a concise AI-generated description of the issue
* **File** — the path and line range where the bug lives
* **Severity** — how critical the issue is, from low to critical
* **Introduced by** — the commit author who added the offending code, derived from `git blame`

Click any bug in the list to open the full AI-generated report. The report includes a plain-language explanation of the root cause, the relevant code excerpt, and a suggested fix you can apply directly.

<CardGroup cols={3}>
  <Card title="Filter by repository" icon="code-branch">
    Scope the list to a single repo when you're doing focused triage on one project.
  </Card>

  <Card title="Filter by status" icon="circle-check">
    Show only `pending`, `resolved`, or `dismissed` bugs — or combine statuses.
  </Card>

  <Card title="Security vulnerabilities" icon="shield-halved">
    Toggle the **Vulnerabilities only** filter to surface findings flagged as security risks.
  </Card>
</CardGroup>

## Triaging a bug

Once you've read the report for a bug, take one of two actions:

<Steps>
  <Step title="Resolve the bug">
    Click **Resolve** after you've addressed the issue in your code. Detail marks the bug as `resolved` and removes it from your pending queue. You can reopen a resolved bug at any time if a fix gets reverted.
  </Step>

  <Step title="Dismiss the bug">
    Click **Dismiss** if the finding isn't actionable. You must choose one of the following reasons before the dismissal is saved:

    | Reason        | When to use                                                      |
    | ------------- | ---------------------------------------------------------------- |
    | **Not a bug** | The AI flagged something that is intentional or correct behavior |
    | **Won't fix** | The issue is real but your team has decided not to address it    |
    | **Duplicate** | Another finding or ticket already tracks the same issue          |
    | **Other**     | Any other reason — add optional notes to explain                 |

    Dismissed bugs are suppressed in all future scans for that repository. They won't resurface unless you explicitly reopen them.
  </Step>
</Steps>

<Note>
  Dismissals are permanent until manually reopened. If you're unsure whether a finding is valid, consider leaving it as `pending` until you've reviewed the relevant code.
</Note>

## Stats & reporting

The overview section of the dashboard gives you a snapshot of your repository's code health:

| Metric            | What it means                                          |
| ----------------- | ------------------------------------------------------ |
| **Total found**   | All bugs Detail has ever detected across your repos    |
| **Outstanding**   | Bugs currently in `pending` state that need attention  |
| **Fixed**         | Bugs marked `resolved`                                 |
| **Dismissed**     | Bugs your team has explicitly closed without fixing    |
| **Repos covered** | The number of repositories Detail is actively scanning |

Track these numbers over time to measure whether your codebase is getting healthier. A growing "outstanding" count alongside a stable "fixed" count is an early signal to increase triage cadence.

## Triggering scans

Detail automatically scans your repositories on every push to your primary branch. You can also kick off an on-demand scan at any time:

<Steps>
  <Step title="Open the repository">
    Navigate to the **Repositories** tab and find the repo you want to scan.
  </Step>

  <Step title="Click Scan Now">
    Click the **Scan Now** button on the repository row. Detail queues the scan immediately.
  </Step>

  <Step title="Wait for results">
    Scan results appear in your findings list within minutes. You'll see new bugs added to the `pending` queue as soon as the scan completes.
  </Step>
</Steps>

<Tip>
  For bulk triage and automation, use the CLI or the REST API instead of the dashboard. Run `detail bugs list` to pull your pending findings into a terminal workflow, or pipe results into your own scripts.

  ```bash theme={null}
  # List all pending bugs for a repository
  detail bugs list usedetail/my-repo --status pending

  # Close a specific bug as dismissed
  detail bugs close bug_abc123 --state dismissed --dismissal-reason not_a_bug
  ```
</Tip>