On this page, “persistent” refers only to the code review comment described in How it works. It’s unrelated to the PR summary’s Standalone comment setting and to CI failure feedback’s own
persistent_comment setting, since each applies to a different comment.Why use persistent review comments
Persistent review comments help teams:- Keep pull request conversations clean
- Track progress across commits more easily
- Reduce noise during iterative reviews
How it works
- With every new commit, Qodo updates the existing review comment.
- If a new issue is introduced in a new commit, it appears as an additional finding marked with a ⭐️ New label.
- All findings are visible directly in the pull request code review.
- Qodo also posts a “Code review by qodo was updated up to the latest commit” message in the pull request each time it updates the comment. To disable this, see Persistent comment notification below.
- Qodo keeps a Previous reviews section in the comment, showing the history of past review runs. See Previous reviews for how to read it.

.pr_agent.toml file.
Enable persistent review comments using the Qodo portal (Recommended)
Navigate to Configurations > Workflow > Code review and configure Review every push. Navigate to Configurations > Display > Notification comments and configure Persistent comment notification. These settings apply to all connected repositories unless overridden at the repository level. See Portal configuration.Enable persistent review comments using .pr_agent.toml
Review every push
Add the following inside your relevant git provider section in.pr_agent.toml. Do not include this in multiple provider sections.
Example (GitLab):
Persistent comment notification
Set the following in the[review_agent] section:
See Configure using .pr_agent.toml file.