> 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/agent-centric-development-cycle/how-to-guides/solve-issues/backlog-fix-suggestions.md).
# Backlog fix suggestions
> **Note:** The SonarQube Remediation Agent is a [Beta](https://docs.sonarsource.com/sonarqube-cloud/appendices/product-release-lifecycle#beta) feature available with the Team (annual) and Enterprise plan accounts. It's free during the beta phase and will be a paid feature when it moves to [General Availability](https://docs.sonarsource.com/sonarqube-cloud/appendices/product-release-lifecycle#general-availability). To learn more about the terms & conditions, please see our legal page about features in [Early Access](https://www.sonarsource.com/legal/early-access/).
Assign issues to the SonarQube Remediation Agent and generate AI CodeFix suggestions in SonarQube Cloud.
*AI features are only available in SonarQube Cloud Team and Enterprise plans*. See the [Subscription plans](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/subscription-plans) page for more details*.*
## Automated backlog remediation
The SonarQube Remediation Agent can run on a schedule, automatically proposing fixes for eligible issues in your main branch without manual assignment. When triggered, the agent opens pull requests in your repository on your configured schedule, grouped by rule key and file type, the same way it does for issues you assign manually. Each scheduled run opens one pull request for up to 5 issues in every selected repository.
An organization admin enables scheduled runs by selecting **Automated backlog remediation** when enabling the Remediation Agent on the **AI capabilities** page. For step-by-step instructions, see the [Enable your agent](/agent-centric-development-cycle/how-to-guides/administer-ac-dc-features/remediation-agent.md#enable-your-agent) article on the SonarQube Remediation Agent page. Once enabled, set the frequency (daily or weekly), the time, and the timezone at which the agent runs. To cap how many open pull requests the agent keeps active, set a limit under **Pause when open PRs reach**, or select **Don't pause**. These organization-level settings apply to all projects where the agent is enabled.
Project admins have the same controls and can override or disable scheduled runs for individual projects. Navigate to *Your Organization* > *Your Project* > **AI capabilities** to manage project-level settings. Project settings take precedence over the organization settings.
Scheduled runs are visible on the **Agent activity** page.
## Assigning issues to the agent
Reduce technical debt by selecting issues from your main branch and letting the SonarQube Remediation Agent propose fixes in new pull requests (PR). The **Assign to Agent** button on the **Issues** page lets you send selected issues to the agent so it can generate a fix proposal for you to review.
The **Backlog fixes** feature runs *only on the main branch*. It must be enabled by selecting **Backlog fixes** from the **AI capabilities** page in SonarQube Cloud. For step-by-step instructions to enable the **Backlog fixes**, see the [Enable your agent](/agent-centric-development-cycle/how-to-guides/administer-ac-dc-features/remediation-agent.md#enable-your-agent) article on the SonarQube Remediation Agent page.
Only eligible issues in your main branch can be assigned to the agent. If you select a mix of eligible and non-eligible issues, a warning appears and you are reminded that only eligible issues will be sent to the service. The **Assign to Agent** button stays greyed out until at least one eligible issue is selected, and you can't assign more than 20 issues at one time. For a list of unsupported rules, see the [Requirements and limitations](/agent-centric-development-cycle/how-to-guides/administer-ac-dc-features/remediation-agent.md#requirements-and-limitations) article on the SonarQube Remediation Agent page.
When you select **Assign to Agent**, the agent opens a new pull request in your repository, authored by the SonarQube Remediation Agent. Fix suggestions are grouped together in PRs, organized by rule key and file type; one PR will be opened for each rule key and/or file type. An estimated time to fix notification will pop up and the agent's activity will be visible on the **Agent activity** page when the PR is available.
1. Navigate to your project’s **Issues** page.
2. Check that you are on the `main` branch.
3. Select issues from your backlog that you want the agent to fix.
4. Select **Assign to Agent** to send eligible issues to the SonarQube Remediation Agent.
**Backlog fixes** are only available when addressing issues in your main branch. See the [Main branch analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/main-branch-analysis) page for information about the main branch **Summary** page.
## Reviewing agent fixes
The PR summary includes issue information in the same format you expect to see in an issue’s rule description from any SonarQube product. The agent’s fix proposal is delivered in a unique commit for each issue, ready for an engineer to review.
The SonarQube Remediation Agent's PR comment will have a list of **Fixed Issues** with information that includes the issue's rule description and the accompanying information as found with every SonarQube rule.
> **Note:** Azure DevOps limits pull request descriptions to 4,000 characters. When the agent fixes several issues in one pull request and the full description would exceed that limit, it shortens the description: each issue keeps its rule, title, and a **View issue** link, while the detailed explanation is dropped to conserve characters. An indicator marks that more issues were fixed than the description lists in full.
## Agent activity
To review the SonarQube Remediation Agent's activity, go to *Your SonarQube Cloud Project* > **Agent activity**. From there you'll see the agent's:
* Status/duration: Time the agent spent to generate fixes.
* Started: When the agent is triggered by the **Automated backlog remediation** schedule, by selecting **Assign to Agent** on the **Issues** page, or by selecting **Fix automatically** in the **Quality Gate failed** comment on a pull request.
* Source: Where the agent is working. *Backlog fixes* means that the agent is working on issues found in your main branch; or a link will be provided to the branch where you first called the agent.
* Outcome: A link to the agent's PR.
* PRs made for *Backlog fixes* will be on your `main` branch.
* PRs made for *Pull request fixes* will be made on your branch. See [Engage with the agent](/agent-centric-development-cycle/how-to-guides/solve-issues/pull-request-fix-suggestions.md#engage-with-the-agent) for details.
## Agents in your pull request
Get AI-generated fix suggestions in your pull request for C#, Java, JavaScript/TypeScript, and Python projects when the quality gate fails with new issues introduced. See the [Pull request fix suggestions](/agent-centric-development-cycle/how-to-guides/solve-issues/pull-request-fix-suggestions.md) page for the full details.
## Related products
For AI-powered pull request review automation, see [Gitar](https://docs.gitar.ai), a separate Sonar product.
---
# 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:
```
GET https://docs.sonarsource.com/agent-centric-development-cycle/how-to-guides/solve-issues/backlog-fix-suggestions.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.