A finding is review feedback anchored to the relevant code. It can include a severity, explanation, and supporting evidence. Findings remain open until you record how they were handled.
Finding states
Section titled “Finding states”| Action | Use it when… | What it records |
|---|---|---|
| Resolve | You addressed the issue in the code. | The finding is resolved. |
| Dismiss | You do not intend to change the code for this finding. | A false positive, accepted risk, or deliberate decision not to fix it. |
| Reopen | A previous decision no longer applies. | The finding is open for another pass. |
Resolve does not ask an agent to change the code. Make the change first, then resolve the finding to record the outcome.
When you dismiss a finding, Desktop asks for one of three reasons:
- False positive — the reported problem does not apply.
- Won’t fix — the issue is understood but will not be changed.
- Accepted risk — the tradeoff is intentional.
Add a note when the reason would not be obvious to someone reopening the review later.
Add your own comments
Section titled “Add your own comments”Desktop lets you add feedback that the automated review did not produce. Anchor a comment to a file and line when possible, or add a general comment when it applies to the review as a whole. Comments can carry evidence such as screenshots, recordings, links, and text notes.
Submit the review
Section titled “Submit the review”Choose Submit review after you have worked through the findings and added your feedback. EV renders the open findings, comments, and recorded decisions as Markdown for the waiting terminal and copies it to the clipboard.
Submitting is the handoff step. It does not mark every open finding as resolved and it does not make code changes on its own.