> 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.

## Requesting fixes

Use the SonarQube Remediation Agent to propose fixes for eligible Hunter Agent findings in your main branch. In addition to your Hunter Agent subscription, your organization needs a Remediation Agent subscription. An organization admin must enable **Manual backlog remediation** and configure an LLM provider key. See [Administer the Remediation Agent](/sonarqube-cloud/administering-sonarcloud/ai-features/administer-remediation-agent.md).

Your project must be private and bound to GitHub, GitLab.com, or Azure DevOps. For platform requirements and restrictions, see [Supported DevOps platforms, languages, and issues](/sonarqube-cloud/administering-sonarcloud/ai-features/administer-remediation-agent.md#supported-devops-platforms-languages-and-issues).

Only findings with an **Open**, **Confirmed**, or **Accepted** status can be assigned.

To request a fix for one finding, select **Fix with Agent** in its issue row or on its details page.

To request fixes for several findings:

1. Open your project's **Issues** page and select the main branch.
2. Filter by the `hunter-agent` tag and **Fixable by Agent** to find eligible Hunter Agent findings.
3. Select the findings you want to fix, then select **Fix with Agent**.
4. Open **Agent activity** to follow the runs. When a fix is available, open the linked pull request or GitLab merge request and review the changes.

For assignment limits and details about reviewing fixes, see [Backlog fix suggestions](/sonarqube-cloud/managing-your-projects/issues/with-ai-features/backlog-fix-suggestions.md#assigning-issues-to-the-agent).

## 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.