Changelog

Improvements & New Features

🗑️ Delete repo-specific configurations

You can now delete individual configurations for any repository directly from the dashboard.

This makes it easier to reset a repo’s settings and have its PRs reviewed using the team’s global configuration instead.

⚙️ Review Cadence control

Some teams reported too many comments being triggered when multiple commits were pushed to the same PR.

To fix that, we’re introducing Review Cadence — a new setting that lets you define when Kody should run re-reviews after the initial one. This helps reduce noise and gives you more control over your review flow.

You can choose from three modes:

• Automatic – Kody re-reviews on every new push (default behavior)
• Auto-Pause – pauses if too many commits happen in a short time; resumes with @kody start-review
• Manual – no automatic re-reviews; Kody only reviews when manually triggered

Improvements & New Features

🔀 Combined severity filter

Now you can merge suggestions from different severity levels into a single filter, giving you precise control over how many comments each category generates.

🐞 Bug Fixes

• Fixed an issue that prevented Kody from reviewing after 30 commits on an open GitHub PR.

Improvements & New Features

📦 Kody Rules with full PR scope

Kody Rules can now run with full pull request context, instead of analyzing files in isolation. With this update, rules can access the PR title, description, file list, and complete diffs — making it possible to write more powerful and contextual validations.

Examples of what you can now do:

• Flag new services that don’t have corresponding tests
• Suggest README updates when business logic changes
• Require meaningful PR descriptions when they’re missing or too short

This change gives Kody deeper context and enables more relevant suggestions across your codebase.

🏗️ Kody support outside organizations

You no longer need to be inside an organization to use Kody. It now works with individual repositories — whether personal projects, test environments, or any repo not linked to an org on GitHub, GitLab, Bitbucket, or Azure DevOps.

This update removes a key limitation and makes Kody more flexible and accessible. No extra configuration needed — it just works within your existing review flow.

🐞 Bug Fixes

• Fixed an issue where the dev name appeared as N/A in the weekly summary email.

Improvements and New Features

✨ Kody Issues: automatically track unimplemented suggestions

You can now automatically track and manage Kody suggestions that weren’t implemented in closed PRs. Kody Issues works like sonar—giving you a clear view of pending improvements and ensuring critical feedback isn’t forgotten.

• Automatic tracking: captures suggestions not applied when the PR is closed
• Smart resolution: marks as resolved automatically when the suggestion is implemented in a future PR
• Advanced filtering: save custom views by status, severity, and category
• Zero setup: works natively in your code-review flow, no configuration required

Email notification for new rules created for import

Whenever new rules are generated for import, every company user now gets an automatic email. No one misses important updates, and new rules are imported without relying on manual reminders.

Configurable severity filter and suggestion limit for Kody Rules

The Suggestion Control filter now lets you decide whether the severity filter and suggestion limit apply to Kody Rules. By default, Kody Rules are no longer filtered automatically—the team decides when to apply it. 😉

Git Settings page layout improvement

We updated the Git Settings page layout to make it easier to view and manage connected repositories. The interface is clearer and now includes confirmations before actions like removing repositories or resetting the integration.

Cockpit UX

Added a new visual treatment when the Cockpit has no historical data.

🐞 Bug Fixes

• Fixed issue where Kody didn’t resolve comments on already implemented suggestions.
• Fixed error loading metrics in the Cockpit.
• Adjusted suggestion limit: setting it to 0 now sends all suggestions, as documented.
• Fixed Kody Rules link showing up in suggestions from other categories.
• Fixed import control of Kody Rules that wasn’t functioning.
• Fixed severity-level control of Kody Rules that was broken.

Improvements and New Features

Direct link to Kody Rules

Kody now includes a direct link to the rule when it finds a violation. This makes it easier to understand the issue and share context with the team.

Onboarding checklist

We added a quick-start checklist to help new users after setup. It highlights the most important first steps to get value from Kodus right away.

OpenAI model override for self-hosted users

Self-hosted instances can now override any of Kody’s models using your own OpenAI API credentials — bringing full flexibility to customize Kody’s behavior.

Forgot password

You can now recover your account password via the login screen.

Increased file limit

The hard limit of files per review was raised from 200 to 500.

Improved UX

Better error handling and loading states across the platform to make the experience smoother and more transparent.

Bug Fixes

• Minor improvements to the model for more accurate suggestions
• UI fixes and small improvements across the app

Improvements and New Features

UI Rebranding

We launched a new version of the interface, more aligned with our brand and focused on providing better contrast and easier navigation on the platform.

New Kody Rules Languages

We added PHP, Go, and Vue to the Kody Rules libraries. You can now like your favorite rules and help strengthen the community!

Azure DevOps

Kody now performs reviews directly on Azure DevOps too! 🙂

Better Workflow Control When Approving Suggestions

Kody now marks a suggestion as resolved whenever it’s implemented — and only marks everything as approved when all suggestions are truly resolved.

Bug Fixes

🐛 Kodus AI and Web

• Fixed an issue where trial days were not displayed correctly.
• Fixed an issue with inviting workspace editors.
• Fixed a token overflow issue caused by embeddings.

Kodus Installer

• Fixed .ENV.Example and installation script issues.