Changelog

News & Improvements

New Code Review Engine

Now you can choose between the current review flow or use the new code review engine, which is much more focused.

This new engine focuses the review on five critical areas:

• Bug: actual bugs or defects in the code
• Security: vulnerabilities that compromise the project
• Performance: efficiency and performance issues
• Breaking Changes: changes that break compatibility
• Cross-file: inconsistencies detected across multiple files in the PR

Everything outside of these categories, such as style, conventions, or internal standards, is now handled by Kody Rules, which can be customized by your team.

Suggestions now come with severity assigned, respect the filters configured by the customer, and keep the safeguard active. The result is a review that is more accurate, clean, and focused on what really needs to be fixed.

Kody Rules Library in Packs

We released the new Kody Rules library, now organized into thematic packs. This makes it easier to explore, choose, and import only the rules that make sense for your team.

In addition, the library has been expanded with several new predefined rule sets, ready for immediate use.

PR Review Tracking

We added a new dedicated screen to track PRs being reviewed by Kody.

On this screen you can view all ongoing PRs, with details such as branch, author, execution status, and final review result. This makes it easier for teams to monitor what has already been analyzed, what is in progress, and ensure visibility of the review flow in real time.

Automatic association by email domain

Now new users can be automatically associated with an existing workspace based on their email domain.

• During workspace setup, it is possible to configure Allowed Domains and enable the auto-join option.
• If the domain is not public (like gmail.com), it will already be suggested automatically.
• At signup, users with emails from these domains can choose between joining the existing workspace or creating a new one.

This change makes team onboarding easier, reduces workspace duplication, and simplifies the flow for new developers.

Bug Fixes

• Approval status on critical PRs: when a PR had suggestions with critical severity and received new commits without new suggestions, the status incorrectly changed to approve. Now the PR remains blocked until the critical issues are resolved.
• IDE rules sync in mono-repos: rule files in subfolders (e.g., applications/APP/.cursor/rules/) were not being detected correctly when there were configurations at multiple levels. Sync now works together with folders in mono-repos.

News & Improvements

IDE rule synchronization with Kody

Kody can now automatically detect and import rule files that already exist in your repository, coming from tools like Cursor, GitHub Copilot, Claude, Windsurf, Sourcegraph Cody, OpenCode, Aider, and even internal folders of code standards.

With this, Kody starts respecting the code standards your team already maintains, without requiring manual setup. Just enable Auto-sync in the settings so Kodus can scan your repository, generate Kody Rules automatically, and keep everything updated every time a PR is closed.

This synchronization covers:

• New files → become new Kody Rules

• Changes → update existing rules

• Removals → delete the corresponding rules

This way, what already exists in your IDE flow or documentation is used directly in Kody’s code review.

Repository Rules

You can now create Kody Rules directly in the repository, using markdown files versioned along with the code.

These rules are automatically detected and synchronized with the Kodus web interface, allowing you to keep clear and shared standards across the team. Changes are applied whenever a PR is closed — whether adding, updating, or removing rules.

📌 Important: To use Repository Rules, you need to have Rule File Detection enabled in your settings. The same synchronization mechanism that detects IDE rule files also processes repository-based rules.

In practice, just add .md files under .kody/rules/** or rules/**, following the supported template (with title, scope, paths, severity, and instructions). This allows you to create anything from simple style rules to test requirements for new endpoints.

PR summary settings after new commits

You can now define how Kody should update the PR summary when new commits are added after the PR has already been opened.

You can configure it globally or per repository between three options:

• Do nothing (default): no new summary is generated.

• Replace Kody’s summary: replaces Kody’s current summary with a new one.

• Concatenate new summary: adds the new summary to the existing one, creating a history separated by lines.

This flexibility helps teams that prefer to keep only the latest state of the PR or those who want to visualize the evolution of the summary throughout the commits.

Mono-repo support in configs

You can configure rules and code review behaviors at the folder level inside a repository. This gives more flexibility to teams working in large mono-repos, allowing them to apply specific configurations for different domains or services without having to limit everything to the repo’s global level.

In practice, you can:

• Select a specific folder when adding configurations.

• Create Kody Rules linked to files or PRs considering the folder’s fixed path.

This makes it easier to maintain different standards in distinct parts of the same repository, without losing organization.

Draft PR Review Execution Settings

You can now choose whether Kody should run automatic reviews on PRs marked as Draft.

The setting can be applied globally or per repository. When disabled, reviews only happen when the PR leaves Draft and is ready for review.

Bug Fixes

• Log recording in Code Review Settings: fixed saving and updating of settings, which now properly generate logs.

• User invites: when trying to invite someone already linked to another organization, the system used to display a success message; it now shows the correct error message.

• Kody Rules after repository removal: rules linked to removed repositories or directories no longer remain active in the database.

• Kody Rule generation: a parser error made prompts run in fallback twice; execution now happens only once, with JSON properly processed.

• Repository configuration deletion: data was not being deleted along with the integration; it is now properly removed.

• Fixed issues with session saving

New Features & Improvements

Repository Filter in the Cockpit

No more looking at your entire team as one big block.

You can now filter metrics by repository in the Cockpit and analyze each project’s performance in isolation.

Want to know which service has the highest lead time? Or where the bug rate is dropping? Just select the repo and see exactly what’s going on.

PR Summary Preview

You can now view a full PR Summary preview directly in Kodus — no need to open the PR in your version control platform.

Simply select a PR, and Kody will show a clear summary of the changes and their impact on the project.

Customizable PR Messages

Now you can tailor Kody’s PR communication to match your team’s style — from the initial “review started” notice to the final report.

Choose the tone, the details, and the format, and decide which context to include (such as changed files and a summary of changes) in each message.

Activity Log Screen

A complete history of everything happening in your organization — who did it, what they did, and when.

The new Activity Log screen shows actions like adding or removing repositories, changing settings, and editing Kody Rules, with date filters and search by user or description.

Ignore Merge Commits and Push Summaries

Kody will no longer update the PR summary with every push — it’s generated only when the PR is opened.

If a push is just a merge with no relevant changes, no new review will be triggered.

Bug Fix

• Fixed an issue where the link to Kody Rules wasn’t working properly.

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.