How to run remediation on an issue
Go from a detected issue to a reviewed pull request without leaving Hud.
Before you startRemediation must be enabled for your account, GitHub must be connected with the repository behind the affected service reachable, and the issue must be eligible for remediation.
1. Open the issue
Navigate to Issues and select the issue you want to fix.
The page opens with What Happened at the top: a short summary of the problem and the error-rate graph. Below it sits the remediation block with Root Cause and Fix.
2. Start the run
Select Run Remediation.
The primary action changes to Remediation in progress and is disabled while the run is active. Root Cause moves to Generating.
You do not need to stay on the page. The run continues on its own, and the sections update as each step finishes.
3. Read the root cause
When Root Cause reaches Ready, it shows a short preview of why the issue is happening, plus a compact forensics card as supporting evidence.
Select the section to open the drawer with the full write-up. Use Full forensics view on the forensics card to see the complete captured execution context.
Read this before the pull request lands. If the root cause is wrong, the fix built on top of it will be wrong too, and this is the cheapest point to catch it.
4. Review the proposed fix
When Fix reaches Ready, it shows a preview of the proposed change, the linked GitHub pull request, and the list of changed files.
Select Review PR to open the pull request on GitHub in a new tab. Review it the way you would review any teammate's pull request. Hud proposes the change; it does not merge it.
5. Merge and confirm
Merge the pull request in GitHub. The Fix section then shows the merged pull request, and the primary action becomes View Merged PR.
6. Leave feedback
Use the thumbs up or thumbs down on Root Cause and Fix, and add free text if something was off. This is the signal the team uses to tune the agent.
What you'll see at each stage
| Run state | Root Cause | Fix | Primary action |
|---|---|---|---|
| Not started | Pending | Pending | Run Remediation |
| Root cause running | Generating | Pending | Remediation in progress (disabled) |
| Fix generating | Ready | Generating | Remediation in progress (disabled) |
| Pull request opened | Ready | Ready, with PR and changed files | Review PR |
| Pull request merged | Ready | Ready, merged | View Merged PR |
| A step failed | Stopped, or Ready if it got past this step | Stopped or Pending | Retry Remediation |
Troubleshooting
| Problem | What to do |
|---|---|
| Root Cause and Fix are not shown at all | The issue is not eligible for remediation. Use Get Prompt to Fix and run the fix in your own coding agent |
| A section shows Stopped | Open the drawer to read the failure reason, then select Retry Remediation |
| No pull request was opened | Check that GitHub is connected and the repository behind the service is reachable. Then retry the run |
| The pull request was closed without merging | Fix shows it as closed without merge. Select Retry Remediation to start a fresh run |
| The root cause is wrong | Give it a thumbs down with a note, then use Get Prompt to Fix to drive the fix yourself |
| You resolved or muted the issue while a run was going | The run finishes anyway and its result is still shown |
Good to know
- Get Prompt to Fix stays available in every state, so the manual path is never blocked.
- A run cannot be cancelled once started.
- An issue can accumulate several runs over time. The page shows the latest one.
For the mechanics behind each step, see How Remediation Works.
Questions about remediation? Chat with our support team or email us at [email protected]
Updated about 2 hours ago