Skip to main content
The severity threshold (formerly Review filters, and before that Suggestion Control) decides which of Kody’s findings actually get posted. In the sidebar, open Code review → What to review; the settings are in the Minimum severity to post card. They can be set at the global, repository, or directory level — see Config Inheritance & Overrides.

​
Minimum severity to post

Kody assigns a severity to every suggestion and only posts the ones at or above the level you pick on the slider. The default is Medium. Kody still finds lower-severity issues; it just does not comment on them.
Too much noise on a big PR is usually a severity problem, not a volume problem. Move to High before reaching for anything else — you keep every real bug and drop the nitpicks. See Reduce code review noise.

​
Apply the threshold to Kody Rules

A toggle in the same card, off by default.
  • Off — Kody Rules findings bypass the severity threshold. A rule your team wrote is always reported, whatever severity it lands on.
  • On — Kody Rules go through the same severity threshold as every other suggestion.
Leave it off unless your rules are producing more noise than signal. The whole point of a Kody Rule is that your team already decided it matters.
In kodus-config.yml these two settings live under suggestionControl:
Remember that the file is only read once you enable kodusConfigFileOverridesWebPreferences — see General.

​
Other ways to cut noise

The severity threshold is a blunt instrument. When you need something more targeted:
  • Ignored files — skip generated code, lockfiles, and vendored directories entirely. See General.
  • Categories — turn off a whole category (e.g. Performance) with its switch on What to review, for repositories where it isn’t useful.
  • Directory-level config — apply a stricter or looser threshold per folder in a monorepo. See Directory Level Config.
  • Kody Rules — encode what your team actually cares about, so the signal comes from your standards instead of generic advice.