Skip to main content
To stop seeing daily tips in your code review, disable Show tip of the day under Comment parts on the Display tab 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.See Chat with Qodo in your pull requests for the full guide.
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.See Chat with Qodo in your pull requests for the full guide.
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.See Chat with Qodo in your pull requests for the full guide.
Displayed labels controls which labels appear on each finding (severity, finding type, finding category, relevance), and Label style controls whether they show as icon and text or icon only. Find both in the portal under Configurations > Display > Labels, which has a live preview of your review comment.See Configure Qodo using the portal for the full guide.
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.See Remediate findings in your pull request for the full guide.
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.See Remediate findings in your pull request for the full guide.
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.See Generate and manage rules for the full guide.
Turn on the rule miner and Qodo discovers your team’s standards automatically from your code review history, turning them into enforceable rules.See Generate rules from pull request history with Rule Miner for the full guide.
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.See Apply REVIEW.md instructions to code review for the full guide.
Under Advanced comment routing overrides on the Display tab, decide where each severity lands: inline comments, the summary comment, both, or dropped entirely. High-severity findings always stay on at least one surface.See Control review verbosity in pull requests for the full guide.
The description, code snippet, relevance, evidence, and agent prompt can each be set to hidden, collapsed, or expanded, so you can tune the comment from lean to verbose.See Control findings visibility and expansion in pull requests for the full guide.
Every finding can include a copy-paste agent prompt. Hand it to your IDE agent to implement the fix with full context.See Anatomy of a Qodo Code Review for the full guide.
Adjust your Display settings 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.See Configure Qodo using the portal for the full guide.
Enable committable code suggestions to apply Qodo’s fix directly from the inline comment. Supported on GitHub and GitLab.See Commit code fixes directly in the pull request for the full guide.
Prefer not to see the rotating tip on your PR comments? Turn off Show tip of the day in the portal under Configurations > Display > Comment parts. With the daily tip disabled, Qodo stops appending it to your PR summary comments.Open Display in the Qodo portal.
Turn off Show images and animations under Configurations > Display > Notification comments 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.See Configure Qodo using the portal for the full guide.
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 > Findings.See Control findings visibility and expansion in pull requests for the full guide.