Fix with HeyDeer

Start a fix

1. Select Fix with HeyDeer in a GitHub review comment, or Fix findings on the review page in HeyDeer. A link from an individual finding preselects it. Opening the page uses no credits.
2. Choose the findings you want to address. Use Add instructions for any finding that needs extra context, such as an approach to take or behavior to preserve.
3. Start the fix with the button below the selection. The task page shows progress, credits used, and the result. If a fix is already active for this PR, select View fix to open it.

The list includes findings from the PR’s reviews and earlier concerns that still need attention. Findings declined in discussion are excluded. HeyDeer rechecks your selection against the saved source revision and can skip findings that no longer apply.

Review and merge the fix

HeyDeer creates a new branch and opens a PR targeting the original PR’s branch. Read the summary and use View fix PR to inspect the changes. You decide whether to merge them into your original PR.

If no code changes are needed, the task can finish without opening a PR.

The summary describes the changes, skipped findings, local test results, and checks HeyDeer could not run. After merging the fix, request a follow-up review on the original PR, or let its automatic review schedule run. Creating a fix PR alone does not resolve findings or make the HeyDeer Review check pass.

Requirements and limits

Fixes require an open PR with both branches in the same repository and someone with repository write access to start them. Fork PRs are not supported. HeyDeer needs Contents and Pull requests read and write permissions; see GitHub app and permissions. Only one fix can be active per PR.

HeyDeer cannot publish changes to GitHub Actions workflow files in .github/workflows/. A fix containing those changes is stopped before any files are published.

Local checks and CI

Starting a fix lets HeyDeer edit code, install dependencies, and run local checks in an isolated sandbox with public internet access. It uses your workspace and repository instructions and repository guidance, without connecting your MCP servers. See Security for how code execution is isolated.

Your GitHub automation may run on the fix PR. Workflows limited to a base branch such as main may run only after you merge the fix into the original PR. HeyDeer does not wait for CI or automatically retry a fix when CI fails.

Credits and cancellation

Fixes use the workspace’s credits and share execution capacity with reviews. Each fix has the current Standard review minimum charge, then uses credits for the work done. Workspace usage limits apply. See How credits work.

Someone with write access can select Cancel fix until HeyDeer starts saving changes to GitHub. Preparation before the agent starts is not charged; after it starts, cancellation keeps the minimum charge and credits already used. If credits run out, the fix stops and you must request another one.

If the original PR changes

A fix uses the commit and branch saved when you start it. Later commits or closing the original PR do not cancel the task. Check for conflicts before merging. If the target branch is deleted or renamed, use View fix commit to inspect the saved changes and decide how to apply them.