> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/remediate.md).

# Remediate

How Konvu turns exploitable findings into remediation plans and fix pull requests, and how to set it up.

Once triage shows a finding is exploitable, Konvu prepares the fix. For each group of findings it writes a **remediation plan**: what to change, what the change affects, and a preview of the diff. When you accept a plan, Konvu opens a **fix pull request** on your repository.

| Finding type                                                                                                                               | Remediation                                                                                                              |
| ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| [Dependencies (SCA)](/konvu/triage-and-remediation/finding-types/dependencies.md)                                                          | Remediation plans and fix pull requests that upgrade the dependency, with code changes when the upgrade breaks your code |
| [Code (SAST)](/konvu/triage-and-remediation/finding-types/code.md)                                                                         | Remediation plans and fix pull requests with a targeted change in your code                                              |
| [Vulnerability reports](/konvu/triage-and-remediation/finding-types/vulnerability-reports.md)                                              | A fix prompt to copy into your coding agent. No fix pull request.                                                        |
| [Containers](/konvu/triage-and-remediation/finding-types/containers.md), [Secrets](/konvu/triage-and-remediation/finding-types/secrets.md) | None. Rebuild the image, or rotate the credential with its provider.                                                     |

## The Remediate page

Open **Remediate** to see every plan and fix pull request on one board. Every member of your organization can review plans, preview diffs, and accept fix pull requests.

| Column         | What it holds                                                    |
| -------------- | ---------------------------------------------------------------- |
| **To review**  | Plans Konvu prepared and is waiting for you to accept or skip.   |
| **Generating** | Accepted plans. Konvu is writing the fix and running your tests. |
| **Ready**      | Fix pull requests open on your repository, waiting for review.   |
| **Merged**     | Fix pull requests your team merged.                              |

Filter the board by finding type (SCA or SAST) and by repository. Select **Review** to go through the plans in the **To review** column one after another and accept or skip each. See [Remediation Plans](/konvu/triage-and-remediation/remediate/remediation-plans.md).

## Set up remediation

Remediation is configured per repository, next to assessment:

1. **Turn on fix plans.** Open **Agents > Coverage**, then select **Enable…** on a repository and check the **Patcheus** agent. Patcheus prepares remediation plans for that repository. Plans only need read access to your code.
2. **Allow fix pull requests.** Opening a pull request needs an integration with write access: the **Konvu Autofix** GitHub App, or a GitLab integration with write access. See [Fix Pull Requests](/konvu/triage-and-remediation/remediate/fix-pull-requests.md#setup).
3. **Connect private registries** if your dependencies come from JFrog Artifactory (npm, Maven, PyPI). Without registry credentials, Konvu cannot build a complete fix. See [Integrations](https://app.konvu.com/integrations).

The [assessment scope](/konvu/administration/assessment-settings.md) applies to remediation too: Konvu only prepares plans for findings inside the severities you assess.

When a repository has plans turned on but cannot open pull requests, **Agents > Coverage** shows why: assessment is turned off, no write-capable integration exists, or the integration does not cover that repository.

## In this section

* [**Remediation Plans**](/konvu/triage-and-remediation/remediate/remediation-plans.md): What a plan contains, how to review it, and what a partial plan means.
* [**Fix Pull Requests**](/konvu/triage-and-remediation/remediate/fix-pull-requests.md): Setup, how Konvu writes and tests the fix, and supported ecosystems.
* [**Fixes on Developer Pull Requests**](/konvu/triage-and-remediation/remediate/fixes-on-developer-pull-requests.md): Konvu fixes vulnerable dependencies in pull requests your developers open.


---

# 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.konvu.com/konvu/triage-and-remediation/remediate.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.