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

# Findings

> Leapter checks your whole project as you work and lists every problem it finds — jump to each one, or let the Lab Agent fix it.

While you work, Leapter keeps checking your whole project for problems — a value of the wrong type, a call to a Blueprint that doesn't exist, or a private Blueprint that nothing calls. Everything it finds is listed in the **Findings** panel, so you can fix problems before you test or release.

## Open the Findings panel

Click the **Findings** tab in the right sidebar of the [Blueprint Editor](/editor/toolbars-and-panels#right-sidebar). When the project has errors, the tab shows a red badge with their number.

The panel groups the findings by Blueprint. Each finding is either an **error** — something that keeps the logic from working as written — or a **warning** — something that works but is probably not what you intended.

When the project is clean, the panel reads **No findings across this project.**

## Work through a finding

For each finding you can:

* **Go to this finding** — jump to the node or definition it is about. The node also carries a badge in the diagram, so you can spot problems while you read the logic.
* **Fix with AI** — hand the finding to the [Lab Agent](/editing/lab-agent). The agent proposes a fix, and you review it like any other agent change before it is applied.

Leapter re-checks the project after every change. To run a full check yourself, click **Re-check the whole project**.

<Note>
  Findings don't stop you from editing or testing, so you can work through them in the order that suits you. Resolve them before you [release](/release-and-integrate/releases) a version to production.
</Note>

## What to do next

* **[Test your Blueprint](/test-and-validate/test-your-blueprint)** — run the logic with your own values once the findings are resolved
* **[Test Suites](/test-and-validate/test-suites)** — keep the fixed behavior covered by tests
* **[Lab Agent](/editing/lab-agent)** — ask the agent to review the whole project with `/review`


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