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