> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/with-ai-features/hunter-agent-findings.md).

# Hunter Agent findings

View and work through the findings the SonarQube Hunter Agent raises on SonarQube Cloud.

The SonarQube Hunter Agent runs an AI-powered analysis to find vulnerabilities that require human-like understanding of the code, such as broken access control and business-logic flaws, then raises them as issues you triage like any other.

The Hunter Agent is a product that requires a separate subscription to your SonarQube Cloud Enterprise plan. An organization administrator sets it up before you can use it. See [Hunter Agent (administration)](/sonarqube-cloud/administering-sonarcloud/ai-features/hunter-agent.md).

To learn what the agent detects and how it works, see [Hunter Agent](/agent-centric-development-cycle/in-your-long-living-branches-the-code-maintenance-loop/hunter-agent.md).

## Viewing findings

Each project with the agent enabled has a **Hunter Agent** page in its navigation. This page gives you a results overview: the total number of findings, a breakdown by vulnerability category (broken access control, business logic, and authentication and session management), and the count at each severity within a category.

Select the issues in one of the findings tiles on the **Hunter Agent** page to open the project's **Issues** page filtered to SonarQube Hunter Agent findings. Each category count links to the issues for that category. On the **Issues** page, you can also filter by the `hunter-agent` tag to see all agent findings, or by a per-category tag such as `hunter-broken-access-control` to focus on one category.

Each finding is raised as a vulnerability with a security software quality and an estimated severity, and includes an explanation with **Why is this an issue?** and **How to fix it?** sections. You review, assign, comment on, and resolve these findings like any other issue. See [Managing code issues](/sonarqube-cloud/managing-your-projects/issues.md) to learn how to review issues in SonarQube Cloud.

## Related pages

* [Hunter Agent (administration)](/sonarqube-cloud/administering-sonarcloud/ai-features/hunter-agent.md)
* AC/DC: [Hunter Agent](/agent-centric-development-cycle/in-your-long-living-branches-the-code-maintenance-loop/hunter-agent.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/with-ai-features/hunter-agent-findings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.