Qodo v3.1 mutes ignored review rules and brings analytics dashboard to GA

Automated rule deactivation cuts review noise

The headline change in v3.1 is automated rule deactivation. According to Qodo, a rule can produce feedback regularly without ever leading to code changes. When the same findings are consistently dismissed or left unaddressed, they add noise to the review process and make useful feedback easier to overlook.

Qodo's rule lifecycle system now uses developers' responses to findings to spot rules that teams consistently ignore. Rules that qualify are automatically muted, so their findings no longer appear as comments on pull requests.

The company says the system looks at patterns across merged pull requests and requires enough findings with recorded outcomes before it decides to mute a rule. A single ignored suggestion is not enough. Qodo says this keeps review feedback aligned with what a team actually acts on and reduces the manual work of finding rules that repeatedly generate low-value comments.

Analytics dashboard is generally available

Qodo's new analytics dashboard has moved to general availability and sits directly in the portal. It shows findings raised, findings accepted and acceptance rate, with breakdowns by severity, category, repository and author. Teams can see both how much feedback Qodo produces and how much of it they act on.

Qodo positions the dashboard for two groups. Engineering leaders get an easier way to understand review activity across repositories. Teams that manage code quality get a starting point for investigating patterns, such as which types of findings are being addressed, where findings are concentrated, and where feedback may need a closer look.

Quick search and clearer background reporting

Quick search is meant to make Qodo's many code review configuration options easier to navigate. Users open it with ⌘K on Mac or Ctrl+K on Windows, type what they need and pick a result with keyboard or mouse. Selecting a setting opens the relevant tab or section and highlights the field.

The release also expands background activity reporting. When Qodo is connected to repositories, it syncs repositories, indexes pull request history, discovers relationships between repositories and imports existing rules and skills. Qodo lists three specific improvements:

• Indexing retries: pull request indexing retries on its own after a failure. Background activity now shows whether those retries are still running or have stopped, so users know when to retry manually.
• Unfinished installations: Git installations with an unfinished setup step previously stayed pending without explanation, even after a retry. Qodo now identifies the incomplete setup so users know why syncing has not started.
• Faster problem location: when Qodo reports a problem, the accompanying link leads directly to the installation or repositories that need attention.

What it means for teams using Qodo

The changes in v3.1 focus on everyday handling of the tool rather than new review capabilities. Automatic muting should reduce the number of comments developers have to dismiss by hand, while the dashboard gives leaders data on whether the remaining feedback is acted on. Quick search and the improved status reporting aim to save time during configuration and onboarding, particularly when an installation stalls and the cause was previously unclear.