> 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-server/project-administration/ai-features/remediation-agent.md).

# Remediation Agent

Customize the Remediation Agent's automated schedule for a single project in SonarQube Server 2026.5.

The SonarQube Remediation Agent proposes fixes for the issues found by analysis and opens pull requests for your review and approval. It's available in the Enterprise and Data Center editions and requires a separate subscription. An Instance Admin enables the agent and sets a default schedule for the instance. See [Remediation Agent](/sonarqube-server/instance-administration/ai-features/remediation-agent.md) for the full details.

As a project administrator, you can keep the default schedule or define a custom remediation schedule for your project.

## Customizing the schedule for your project <a href="#customizing-the-schedule" id="customizing-the-schedule"></a>

1. Go to **Project settings** > **AI Capabilities** > **Remediation Agent**.
2. Choose how the project follows the instance schedule:
   * **Use default schedule**: the project runs on the schedule set for the instance. The current default is shown, along with the maximum number of open pull requests.
   * **Customize for this project**: override the default schedule with a custom frequency for this project.
3. If you selected **Customize for this project**, set the **Frequency**, **Day of week**, **Hour**, and **Timezone**, then set **Pause when open PRs reach** or select **Don't pause**.
4. Select **Save**.

A summary confirms the next run time and states that each run opens one pull request for up to five issues in this repository.

You can return the project to the default schedule at any time.

## When the agent isn't available for your project <a href="#agent-not-available" id="agent-not-available"></a>

The page explains why the agent cannot run and, if you're a project administrator, offers the action that resolves it:

| Message                                                               | What it means                                                                                                               | What to do                                                                                                                  |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| The Remediation Agent is not enabled for this project                 | The agent hasn't been turned on for this project.                                                                           | Project administrators can select **Enable the Remediation Agent for this project**. Otherwise, contact your administrator. |
| This project isn't bound to a repository                              | The agent has no repository to clone or open a pull request against.                                                        | Project administrators can select **Set up project binding**. Otherwise, contact your administrator.                        |
| Automated backlog remediation is not enabled for this project         | The scheduler is off, so no scheduled runs happen. Manual assignment is unaffected.                                         | Project administrators can select **Enable Automated backlog remediation**. Otherwise, contact your administrator.          |
| Manual backlog remediation is not enabled for your SonarQube instance | Users cannot assign issues to the agent anywhere on this instance. This is an instance-level setting, unlike the row above. | Project administrators can select **Enable Manual backlog remediation**. Otherwise, contact your administrator.             |

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Remediation Agent](/sonarqube-server/instance-administration/ai-features/remediation-agent.md)
* [Backlog fix suggestions](/sonarqube-server/user-guide/issues/with-ai-features/backlog-fix-suggestions.md)
* [Remediation Agent](/agent-centric-development-cycle/in-your-long-living-branches-the-code-maintenance-loop/remediation-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-server/project-administration/ai-features/remediation-agent.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.