Feature request
What happens today
With pr_reviewer.persistent_comment: true (the default), every re-run of /review edits the existing comment in place and replaces its body with the latest review. When a finding from a previous run is gone, because the code was fixed, it simply disappears from the comment. There's no trace it ever existed, and no signal that it was resolved.
Why that's a problem
The review comment is the entire record of the audit on the PR. Overwriting it throws away the history:
You can't tell what was flagged earlier, how the author addressed it, or that it moved from "open" to "resolved", only the latest snapshot survives.
If someone replied to the review in a thread, that reply is now stranded under a comment whose content has changed. It reads as if the person is answering a finding that isn't there anymore.
Setting persistent, comment: false avoids the overwrite (each run posts a fresh comment, so the old one stays), but then a full review piles up on every push, and there's still no explicit "this got fixed" signal, only the absence of the finding in the newer comment.
What I'd like instead
Treat findings as items that carry a state across runs, rather than a comment body that gets wiped each time:
When a finding from an earlier run is no longer detected, mark it as resolved instead of dropping it silently, keep its text so the reader can see it transitioned.
Ideally the persistent comment shows the active findings plus a collapsed "resolved" section, so the trail is kept without bloating the comment over time.
A reply tied to a finding shouldn't be orphaned when that finding changes state.
The goal is a comment that reads like a living audit log, what was found, what got fixed, what's still open, instead of a snapshot that erases its own past on each re-run.
Contributing
If you're open to it, I'd be glad to put up a PR implementing this.
Motivation
CodeRabbit already does this and it works really well. When someone reads the PR history later, they can see what was flagged, how it was addressed, and, just as important, that the reviewer ran again and explicitly marked the issue as resolved. That trail is genuinely useful: a person auditing the PR after the fact understands what happened and how it was fixed, and can trust that the bot re-checked and confirmed the resolution, instead of guessing from the mere absence of a comment. Today PR-Agent loses all of that, because the review is a snapshot that overwrites itself on every run.
Feature request
What happens today
With
pr_reviewer.persistent_comment: true(the default), every re-run of/reviewedits the existing comment in place and replaces its body with the latest review. When a finding from a previous run is gone, because the code was fixed, it simply disappears from the comment. There's no trace it ever existed, and no signal that it was resolved.Why that's a problem
The review comment is the entire record of the audit on the PR. Overwriting it throws away the history:
You can't tell what was flagged earlier, how the author addressed it, or that it moved from "open" to "resolved", only the latest snapshot survives.
If someone replied to the review in a thread, that reply is now stranded under a comment whose content has changed. It reads as if the person is answering a finding that isn't there anymore.
Setting
persistent, comment: falseavoids the overwrite (each run posts a fresh comment, so the old one stays), but then a full review piles up on every push, and there's still no explicit "this got fixed" signal, only the absence of the finding in the newer comment.What I'd like instead
Treat findings as items that carry a state across runs, rather than a comment body that gets wiped each time:
When a finding from an earlier run is no longer detected, mark it as resolved instead of dropping it silently, keep its text so the reader can see it transitioned.
Ideally the persistent comment shows the active findings plus a collapsed "resolved" section, so the trail is kept without bloating the comment over time.
A reply tied to a finding shouldn't be orphaned when that finding changes state.
The goal is a comment that reads like a living audit log, what was found, what got fixed, what's still open, instead of a snapshot that erases its own past on each re-run.
Contributing
If you're open to it, I'd be glad to put up a PR implementing this.
Motivation
CodeRabbit already does this and it works really well. When someone reads the PR history later, they can see what was flagged, how it was addressed, and, just as important, that the reviewer ran again and explicitly marked the issue as resolved. That trail is genuinely useful: a person auditing the PR after the fact understands what happened and how it was fixed, and can trust that the bot re-checked and confirmed the resolution, instead of guessing from the mere absence of a comment. Today PR-Agent loses all of that, because the review is a snapshot that overwrites itself on every run.