Skip to main content
To stop seeing daily tips in your code review, disable the daily tips feature from the configurations page in your Qodo portal.
Start any PR comment, review comment, or inline code comment with qodo, @qodo, or /qodo, or open with a greeting like Hey qodo, to chat with Qodo about a finding. Ask it to explain the issue, discuss the suggestion, or ask follow-up questions in natural language. Qodo only responds when addressed, so reviewer discussions are never interrupted.Learn more
Tell Qodo to dismiss a finding and explain why. The finding is struck through and marked as Dismissed in the review comment, so the rest of the team sees the decision.Learn more
Reply to any finding to push back on a suggestion, request a deeper explanation, or refine the recommendation. Your feedback shapes the conversation on the PR.Learn more
The Finding display setting controls how type and category labels appear on findings, from Minimal (type icon only) to Full (type icon, category icon, and full name). Find it in the portal under Configurations > Display preferences, which has a live preview of your review comment.Learn more
Under Configurations > Remediation, turn on the Remediation agent and Qodo fixes review findings for you, delivered as a dedicated fix PR or pushed directly to your source branch. Set an auto-fix severity threshold to control which findings it picks up.Learn more
Type qodo, fix the null pointer issue in this PR and the chat agent applies the fix without you leaving the PR. This is best for targeted fixes where you want control over what changes.Learn more
On the Rules page in the portal, describe the rule you want in plain language, such as “Restrict console.log in prod builds”, and Qodo drafts it for you, complete with examples and severity.Learn more
Turn on the rule miner and Qodo discovers your team’s standards automatically from your code review history, surfacing them as suggested rules for approval.Learn more
Add a REVIEW.md file at your repository root and Qodo applies the review instructions and guidelines it contains on every PR. It is a simple, repo-local way to customize your review.Learn more
Under Verbosity, decide where each action level lands: inline comments, the summary comment, both, or dropped entirely. Critical findings always stay on at least one surface.Learn more
Finding overflow collapses all but the top findings per severity behind a “View more” link, so the summary stays scannable on busy PRs.Learn more
The description, code snippet, recommendation, evidence, and agent prompt can each be set to hidden, collapsed, or expanded, so you can tune the comment from lean to verbose.Learn more
Every finding can include a copy-paste agent prompt. Hand it to your IDE agent to implement the fix with full context.Learn more
Adjust your Display preferences in the portal and a live preview shows exactly how your review comment will render as you change settings, so you can see the result before it ships.Learn more
Enable committable code suggestions to apply Qodo’s fix directly from the inline comment. Supported on GitHub and GitLab.Learn more
Prefer not to see the rotating tip on your PR comments? Turn it off in the portal under Configurations > Display preferences. With the daily tip disabled, Qodo stops appending it to your PR summary comments.Learn more
Turn off images and animations under Configurations > Display preferences and Qodo renders text and markdown equivalents instead of the illustrations, dividers, section badges, and footer logo. Handy for air-gapped setups where the image host is unreachable, or if you simply prefer a plain comment.Learn more
Each block in a finding can be hidden outright rather than just collapsed, so the parts your team never opens stop taking up room in the comment. Set them under Configurations > Display preferences.Learn more