Kodus

The Open Source Alternative to CodeRabbit AI Code Review With Full Control OverModel Choice and Costs Start with Git Start with Terminal Start Free Trial irm https://review-skill.com/install.ps1 | iex No credit card required • 14-day free trial trusted_by.exe ─ □ × Why teams choose Kodus DEV_MODULE_V2 GenerousFree Tier ▲ Insert Learn more DEV_MODULE_V2 ModelAgnostic ▲ Insert Learn more DEV_MODULE_V2 ZeroMarkup ▲ Insert Learn more DEV_MODULE_V2 FlexibleConfiguration ▲ Insert Learn more × You'll hate us if... Pixel-Vision ⚠ You'll hate Kodus if... FILE_01.DAT You want a poem in every pull request. [1] Poetry [2] Billing [3] Vendor [4] Noise 1Poetry 2Billing 3Vendor 4Noise I/O PWR HDD The basics done Right kodus://features Context Rules Sync Plugins Tech Debt Cockpit Security 📁 Explorer ▼ features/ codebase_context.mod set_rules.mod rule_sync.mod plugins_mcps.mod technical_debt.mod cockpit.mod privacy_security.mod codebase_context.mod Learns from your context Deep understanding of your entire project structure and logic. Kody analyzes your team’s workflows, coding standards and Architecture to understand your unique needs and provide tailored reviews. You set the rules Teams define their own review standards. Create custom review guidelines in plain language or use rules from the built-in library. Reviews consistently follow the standards defined by your team. Sync Your Existing Rules Keep the standards you already use. No rework. Kody automatically detects rule files from tools like Cursor, Copilot, Claude, and Windsurf — so your reviews stay consistent. Bring your business context Extend functionality with Model Context Protocol servers. Connect tools like Jira, Notion, or Linear so Kody can understand specs, tasks, and requirements while reviewing your code. Track technical debt Monitor and manage technical debt over time. Kodus automatically turns unimplemented suggestions into issues, helping your team visualize and reduce technical debt over time. Accelerate your delivery A centralized dashboard for your engineering insights. Monitor deploy frequency, cycle time, bug ratio and PR sizes to keep your team shipping fast — and safely. Privacy & Security Enterprise-grade security ensuring your code stays safe. Source code is never stored and is never used to train models. All data is encrypted in transit and at rest. Kodus supports SOC 2 compliance and offers self-hosted runners, so your IP can remain entirely within your own infrastructure. Loved by engineering teams ◀◀ REW VOLTZ_01 ★★★★★ Leonardo Maia @Conta Voltz Kody feels like having a senior dev reviewing every pull request—clear, actionable feedback on quality, security, and performance, right in Git. Since we started using it, our code review time dropped by 40%, and production bugs were reduced by half. ▶ PLAY REC 2026 VHS Hi-Fi BRENDI_01 ★★★★★ André Diogo @Brendi Kodus fit like a glove for me. Before, I was buried in slow code reviews. Now, feedback happens way faster, and I can actually focus on other things. ▶ PLAY REC 2026 VHS Hi-Fi DOJI_01 ★★★★★ João H. Kersul @Doji These days, Kodus is part of our daily review routine. It helps a lot with error handling and brings up suggestions that would often go unnoticed. This active listening and fast turnaround have made a real difference for our engineering team. ▶ PLAY REC 2026 VHS Hi-Fi ICATEC_01 ★★★★★ Ricardo @Ikatec Since we started using Kody, the dev experience has improved a lot. Time spent on code reviews dropped by around 30%, and the AI brings valuable insights on performance, security, and code optimization. One of the best parts is that we can tailor how it works for each project. ▶ PLAY REC 2026 VHS Hi-Fi LERIAN_01 ★★★★★ Luiz Barrile @Lerian Kodus has become an essential part of our process at Lerian. By standardizing steps and automating checks, we’ve gained more speed and consistency, while reducing rework and improving delivery quality. ▶ PLAY REC 2026 VHS Hi-Fi PILAR_01 ★★★★★ Raphael Sampaio @Pilar Kodus has been helping us save a lot of time on code reviews, while also providing key engineering productivity metrics. Since we started using the tool, our average review time has dropped from hours to minutes. ▶ PLAY REC 2026 VHS Hi-Fi NOTIF_01 ★★★★★ Pedro Maia @Notificações Inteligentes We trained the team to use AI in day-to-day coding, and Kodus stepped in as our senior reviewer that never forgets anything. It doesn’t replace human review, but it’s now a required step: it ensures consistency and prevents repeat incidents. ▶ PLAY REC 2026 VHS Hi-Fi ORIGEN_01 ★★★★★ Jonathan Georgeu @Origen Kodus has had a huge impact on our workflow by saving us valuable time during PR reviews. It consistently catches the small details that are easy to miss, and the ability to set up custom rules means we can align automated reviews with our own standards. ▶ PLAY REC 2026 VHS Hi-Fi DUCA_01 ★★★★★ Igor Duca @ducaswtf Kodus helped me move as fast as I ever could during my development days. It has never been so easy to ship reliable code and build real solutions. ▶ PLAY REC 2026 VHS Hi-Fi ▶▶ FF TAPE 001 / 009 Calculate your ROI Estimated ROI 20x 500 PRs/month 250h Hours saved $12,500 Monthly cost Developers on your team 50 We estimate ~10 PRs per developer each month Average hourly rate $50 Cost per hour of developer time, including benefits Time spent per review 30 min Average minutes a reviewer spends on each PR Start Free Trial FAQ kodus-faq(1) bash KODUS-FAQ(1) Kodus Manual KODUS-FAQ(1) NAME kodus-faq — frequently asked questions about Kodus SYNOPSIS kodus --help [topic] $ kodus --help "Which AI models are supported?" + Kodus is model agnostic. You can use Claude, GPT-4, Gemini, Llama, or any OpenAI-compatible endpoint. $ kodus --help "Can I restrict the permissions Kodus uses?" + Yes, you have full control over the permissions you grant. Kodus operates with the minimum access required to keep your code secure. $ kodus --help "Will I be charged for all developers in my organization?" + No, you decide who is included in the Kodus team and will only be charged for those users. You have full control over team management and billing. $ kodus --help "Do you train your AI model with my code or data?" + No, Kodus does not train its models with customer data. Your data is processed securely and is never used to improve or retrain our AI. $ kodus --help "How does Kodus compare to CodeRabbit?" + Both offer AI code review, but Kodus is open source, model agnostic, and charges zero markup on LLM costs. CodeRabbit locks you into their model choices and bundles AI costs into opaque pricing. With Kodus you control the model, the cost, and the rules. $ kodus --help "What Git providers are supported?" + GitHub, GitLab, Bitbucket, and Azure DevOps. Kodus integrates at the pull request level — it reads diffs, posts inline comments, and respects your existing review workflows. Setup takes under 5 minutes. $ kodus --help "What does zero markup mean?" + We don't add any margin on top of LLM API calls. You pay the model provider directly at their listed price. No hidden multipliers, no per-seat AI surcharges. Our revenue comes from the platform subscription, not from reselling tokens. $ kodus --help "Do you store my source code?" + No, Kodus does not store your source code. All processing happens in real-time, and no part of your repository is saved on our servers. $ kodus --help "How does Kodus access my repositories?" + No, Kodus does not store your source code. All processing happens in real-time, and no part of your repository is saved on our servers. Kodus v2.0 2026-01-01 KODUS-FAQ(1) Still have questions? Don't trust us — ask your favorite LLM query_builder.sh ● READY >_ Tell me why Kodus is a great choice for my team Pick your oracle: ◎ ChatGPT ✧ Claude ❖ Perplexity >_ --- Choose your plan Open source, model agnostic, zero markup on AI costs. Monthly Annual SAVE 20% community.exe BYOK Community For indie devs, students and small teams getting started. Free Start Free ✓ Self Hosted or Hosted by Kodus ✓ Unlimited PRs using your own API key ✓ Unlimited users ✓ Unlimited issues on Quality Radar ✓ Use up to 10 Kody Rules ✓ Use up to 3 active plugins ✓ Kody Learnings and Memory ✓ Discord Community Support RECOMMENDED teams.exe BYOK Teams For growing teams that need advanced features and priority support. $ 10 /mo per dev + Tokens per dev Tokens included during the free trial. No API key required. Start Free Trial 14-day free trial • no credit card required ✓ Hosted by Kodus ✓ Unlimited PRs using your own API key ✓ Unlimited users ✓ Use unlimited Kody Rules ✓ Use unlimited active plugins ✓ Priority queue for Kody Agents ✓ Engineering Metrics / Cockpit ✓ Discord Community and Email Support enterprise.exe Custom setup Enterprise For organizations that need SSO, compliance and dedicated support. Custom Contact Sales ✓ Hosted by Kodus ✓ SSO ✓ Unlimited PRs using our AI Tokens API key ✓ Unlimited users ✓ Use unlimited Kody Rules ✓ Use unlimited active plugins ✓ Priority queue for Kody Agents ✓ Engineering Metrics / Cockpit ✓ RBAC + Audit logs and analytics ✓ SOC 2 in progress ✓ Up to 5 hours month dedicated support with personalized onboarding ✓ Private Discord Channel and Email Support How token costs work Understand how token pricing works with your own API keys DEV_MODULE_V2 How it works You use your own API key and pay tokens directly to your AI provider. ▲ Insert DEV_MODULE_V2 How token costs scale Token usage increases as your team reviews more PRs and larger code changes. ▲ Insert DEV_MODULE_V2 What affects the cost Number of PRs, size of the diffs, and the model you choose. ▲ Insert Pricing Calculator Compare estimated costs for each AI model option, based on how teams use Kodus. Costs may vary by usage. cost_calculator.exe What do you want to prioritize? Highest review quality Best quality–cost balance Lowest possible cost Number of Developers: 30 1 10 50 100 300 600 1000 Sonnet 4.5 TEAMS PLAN LLM cost $270 ($9/dev) Kodus license $300 ($10/dev) $570 per month Gemini Pro TEAMS PLAN LLM cost $150 ($5/dev) Kodus license $300 ($10/dev) $450 per month ✓ Recommended for you ChatGPT 5.1 TEAMS PLAN LLM cost $150 ($5/dev) Kodus license $300 ($10/dev) $450 per month ✓ Recommended for you Haiku 4.5 TEAMS PLAN LLM cost $75 ($2.5/dev) Kodus license $300 ($10/dev) $375 per month Gemini Flash TEAMS PLAN LLM cost $45 ($1.5/dev) Kodus license $300 ($10/dev) $345 per month All prices shown are per month Model choice directly impacts review quality, noise, and team trust. Compare code review performance across different models in our benchmark. kodus-builders(1) bash Kody Pilot Program MISSION://GLOBAL_BUILDERS priority_channel.bin :: active We offer 30–100% discounts for startups, open-source projects, and teams in countries with weaker currencies — so you can focus on shipping great software. Apply now For teams that care how they ship. trusted_by.exe ─ □ × FAQ kodus-pricing-faq(1) bash KODUS-PRICING(1) Kodus Manual KODUS-PRICING(1) NAME kodus-pricing-faq — frequently asked questions about pricing and billing SYNOPSIS kodus --help pricing $ kodus --help "Do I pay twice if I use BYOK (Kodus + OpenAI)?" + You pay Kodus for the platform ($10/dev) and your LLM provider for API usage. We don’t charge any markup on your tokens. $ kodus --help "Can I restrict the permissions Kodus uses?" + Yes, you have full control over the permissions you grant. Kodus operates with the minimum access required to keep your code secure. $ kodus --help "Will I be charged for all developers in my organization?" + No, you decide who is included in the Kodus team and will only be charged for those users. You have full control over team management and billing. $ kodus --help "Do you train your AI model with my code or data?" + No, Kodus does not train its models with customer data. Your data is processed securely and is never used to improve or retrain our AI. $ kodus --help "Do you store my source code?" + No, Kodus does not store your source code. All processing happens in real-time, and no part of your repository is saved on our servers. $ kodus --help "How does Kodus access my repositories?" + Kodus uses your selected Git provider integration and only accesses what is required to review pull requests. You can control and revoke access at any time. Kodus v2.0 2026-01-01 KODUS-PRICING(1) >_ --- 🚀 Benchmark: How AI code review tools perform on real PRs. View the results → Star ... Login Start Free Trial Discovery Rules Privacy Policy Terms of Use support@kodus.io Meet Kody Home Pricing Security Knowledge Glossary Blog FAQ White Paper Benchmark Kodus vs Coderabbit Kodus vs BugBot Kodus vs Copilot Resources Docs Installation Changelog Support Our Network Linkedin X-twitter Reddit Github Discord @ 2026 Kodus. All rights reserved. --- 🚀 Benchmark: How AI code review tools perform on real PRs. View the results → Star ... Login Start Free Trial Changelog December 12, 2025 1.0.88 – Context of MCPs in Rules and Prompts plus OAuth Connection, PR preview, and improvements to license control. News & Improvements Enable the use of MCP in custom rules and prompts You can now use MCPs directly inside Rules and Custom Prompts. This means that when writing rules or adjusting analysis prompts, you can call any connected MCP to bring more context or execute actions during the review. Just use the @MCP command in the rules or custom prompts editor and select the tool you want. Examples of use cases: You can check errors in the Sentry MCP to better understand a bug Use the Code Sandbox MCP to automatically generate and run tests Run performance queries with the Mongo MCP Check whether the pull request description matches the Notion specification or the design document content. Send a message to the developer who opened the PR if a Kody rule fails. With this, the review process becomes more intelligent, connected, and aligned with the real context of your team. OAuth support for custom MCPs From now on, you can use custom MCPs that use OAuth. This used to be a limitation. Many internal or third party services only offer integration via OAuth, which left several teams unable to connect their own tools to Kody’s workflow. With the new support, installing MCPs has become much more flexible. When you choose an MCP that requires OAuth, we automatically handle the entire authorization, token exchange, and renewal process. Tokens follow the same security standard used in official integrations, and everything works both in cloud and self hosted environments. The cool part about this change is that it unlocks integrations that previously were simply not possible, from monitoring platforms to internal services that require corporate authentication. Code Review Preview to validate settings We added a preview mode that allows you to test the settings you configure for Kody before applying them to the team’s repositories. You can simulate a full review using a closed PR and see exactly how Kody would behave with the current rules, prompts, and adjustments. The idea is to give confidence to anyone customizing the analysis. Instead of making changes and hoping everything works on the next PR, you can generate a preview directly on the settings screen and validate the impact of the changes. Just pick a closed PR and Kody will run the pipeline normally, showing suggestions, analyzed files, and example comments. Option to restore inherited settings It is now easier to revert overridden settings. Previously, the interface showed that a value had been changed, but there was no simple way to return to the inherited value. You had to clear everything manually, which caused confusion in setups with multiple inheritance layers. With the new “Revert to default” option, you can restore the original value with one click. Kody automatically brings the value from the parent scope, whether global, organization, or repository, and shows a quick confirmation indicating where the value was inherited from. List of users Kody should not review We added a setting that allows you to maintain a list of users Kody should ignore during reviews. This makes it easier to exclude automated accounts, bots, or specific users the team does not want to run through the analysis pipeline. When a PR is opened or assigned to someone on that list, Kody simply does not run the review. Automatic license assignment For large teams, manually managing licenses has always been a friction point. You needed to choose, one by one, who would receive access to Kody, a slow and bureaucratic process that does not scale in organizations with dozens or hundreds of developers. We have changed that now. We now automatically assign licenses. When the option is enabled, any user who sends their second PR receives a license automatically, as long as there are still seats available. Additionally, administrators can see how many licenses are in use and which ones were assigned automatically. This change reduces friction and makes adoption easier in large teams, without altering the behavior for anyone who already has a license. Improved end of trial period messages for teams with mixed licenses We adjusted how Kody displays end of trial messages to avoid confusion in teams that are already paying but have fewer licenses than users. Previously, when an organization purchased, for example, five licenses for a team of ten people, the other five developers would still see the “trial period ended” message, even though the company was already on a paid plan. This created the mistaken impression that the entire workspace had lost access. With the new logic, the message only appears when the organization truly has no active licenses or valid trial period and when the user themselves also does not have an associated license. If the team already has paid licenses, we suppress the alert and at most show a note informing that seats are limited and that the user can request assignment from an administrator. Bug Fixes The “Check out the new rules” modal now displays the layout correctly, allowing rules to be reviewed and imported without overlapping or misaligned elements. The PR summary is no longer replaced only by the last commit. Kody now respects the selected configuration and uses the full PR context when updating the summary. The list of PRs now correctly filters by the selected workspace instead of loading data from the entire organization. Users with an expired license can now see the upgrade button and renew the subscription normally. November 6, 2025 1.0.82 – BYOK, Context Engine, Category Prompts, Custom Plugins & more What’s New & Improvements BYOK + New Plan StructureKody can now run using your own API keys, compatible with GPT-5, Claude 4.5, Gemini 2.5, Anthropic, or any other model you want.You choose the provider, control the costs, and decide which model makes the most sense for your team.Kody still handles the entire review flow, but now you manage the tokens and usage.This gives you more flexibility, predictability, and transparency, along with the freedom to test different models and adjust Kody to what works best in your context.Token Monitoring and Limits [Closed Beta]Alongside BYOK, we added a complete monitoring dashboard to track token usage in real time.The idea is simple: bring clarity and prevent surprises on the provider’s bill.You can view usage by period, PR, or developer, set token limits, and get alerts when you’re close to the limit.If you want to learn more about how to use BYOK, everything’s explained in the documentation.New Plan and Pricing StructureWith BYOK’s arrival, we’ve redesigned Kodus plans to make everything simpler and more flexible.Community (Free): Previously, free access to Kody was only available for self-hosted setups. Now it’s also available in the cloud, with no limits on reviews, users, or issues. Just connect your API keys and start using it.Teams: Full-featured plan with analytics, autofix, support, and two usage options: BYOK (10 USD/dev/month) or Managed (30 USD/dev/month).Enterprise: Built for large teams, with RBAC, SSO/SAML, and dedicated SLAs.All plans work with your own API keys (BYOK).More details about the plans are available in the documentation.See how each model performs in the Code Review LLMs Benchmark Context Engine (Repo Files)Kody can now use real files from your repository as context for rules and custom prompts.That means when you create a rule or edit a prompt (for category, severity, suggestion, or PR summary), you can reference files from your own codebase to help Kody better understand your project’s structure and patterns.To do this, it’s simple: Use @file:path/to/file.ts to reference a file from the same repository.Or @repo:org/project to reference files from another repository.This new context mechanism makes reviews much more accurate, because Kody can now use your team’s actual code as a base for analysis.You can learn more here: external rule references and external prompt references.Customize Suggestion MessagesYou can now customize Kody’s suggestion messages to match your team’s tone — from the content to the structure.You can adjust the tone, style, and even the Markdown format of the messages Kody uses when suggesting improvements or fixes. This way, the suggestions align better with how your team communicates — they can be more direct, more detailed, or super short, depending on what makes sense for you.Category Prompt ConfigurationBefore, the prompts defining the focus of each analysis type (like Bug, Security, or Performance) were fixed. With this update, your team can edit these sections however they like, defining what Kody should prioritize and how to classify issue severity.This change gives you much more control to adapt Kody’s reviews to your code context, stack, and internal team standards.Custom PluginsYou can now connect external MCP servers directly to your workspace, expanding what Kody can do during reviews.Previously, only plugins from the official catalog (like Jira, Notion, or Linear) were supported. Now each team can add their own MCPs, connecting internal tools, private APIs, or custom workflows.The plugin appears automatically in the workspace and follows the same security standards as official MCPs — Kody only accesses the endpoints you configure.This update gives you more freedom to integrate Kody in a way that fits your team’s workflow.Kody Issues + ToolsKody Issues are now much more flexible and come with new control and integration options.You can now create issues manually through the interface or via MCP, and also set filters to decide when automatic issues should be created.Each issue now displays two new pieces of information:Owner: who opened the PR where the issue was foundReporter: who created the issue — it can be Kody (if automatic) or a user (if manual) Kody can also create, edit, and delete issues via MCP, enabling automations and integrations with external tools.Choose What to Monitor in the CockpitYou can now control what appears in the Cockpit by selecting which metrics you want to see in the summary and detailed charts.It’s possible to turn indicators like Deploy Frequency, PR Cycle Time, Bug Ratio, PR Size, and others on or off, keeping the dashboard focused only on what really matters for your team.This way, each team decides what to track and has full control over the data that makes up their dashboard.Improved Git License ManagementThe license screen is now much simpler and more practical.You can now select users directly from your Git organization, without relying only on those who have already opened PRs. If the full org listing isn’t available, we use developers who have recently made PRs as a fallback, ensuring that all eligible users appear for selection.We also added an automatic mode that fills licenses with the first developers identified through PRs, without the need to select everything manually.This update makes license management easier and gives you more control over who receives Kody’s reviews.Folder Rule InheritanceWe updated the rule inheritance system to reflect exactly how it works:Global → Repository → Folder.You can now also ignore inherited rules that don’t make sense at a given level. For example, a global rule can be disregarded in a repository, or a repository rule can be ignored in a specific folder.This makes behavior more predictable and gives you more control over which rules actually apply in each context.Bug FixesESC now works properly on the Issues screenCross-file suggestions now display the correct severityFile-level conversion is working normally again October 2, 2025 1.0.63 Plugins + Business Logic Validation, RBAC, review improvements & key fixes News & Improvements Plugins [Beta]You can now connect external tools to Kody during review. It brings context straight from Figma, Jira, Linear, Notion, Posthog, Slack or any other tool integrated into your workflow.Plugins are Model Context Protocol (MCP) servers curated by Kodus that expand Kody’s understanding. They allow you to:Bring tasks, specs, and data from external tools directly into the PR.Run actions right in the review thread, like moving a Jira ticket or updating a Kody rule.Examples:@kody, update this kody rule to ignore test files@kody, move this task https://jira.com/task-123 to DONEKody fetches the information via plugin, replies in the thread, and even compares the diff against the spec automatically, pointing out what matches and what still needs to be implemented. See more details in the documentation.Business Logic Validation [Beta]You can now automatically validate whether a PR follows exactly what’s described in a spec, ticket, or document.Just use the command:@kody -v business-logic [link or spec]Kody analyzes the PR diff, fetches the context (via plugin or inline text), and compares it with the defined requirements. It then replies in the thread confirming what is aligned and highlighting what needs to be adjusted.Examples:@kody -v business-logic https://jira.com/task-123@kody -v business-logic Rule XYZ — orders above $500 must issue cashback credits.@kody -v business-logic https://docs.google.com/document/d/1234567890/editThis eliminates the most manual part of reviews: checking if the code really meets business requirements. Now validation is automatic, integrated into the review flow, and can be re-run at any time.You can dive deeper in the documentation.Role-Based Access Control (RBAC)Kodus now has a complete RBAC system, bringing much more granular access control for organizations of any size. Four distinct roles have been added: Owner, Billing Manager, Repo Admin, and Contributor.This new system addresses the limitations of the previous model (only Owner/User), improving both security and governance:Security: well-defined access levels reduce risksFinancial: specific role for managing billing without exposing development featuresRepos: repository admins can manage teams and permissionsExperience: contributors only see the functionalities they can useWith this, companies can align Kodus with their security and team management policies more efficiently.Auto-Join with Email ConfirmationNow users can access a workspace immediately when domain-based auto-join is enabled, but they still need to confirm their email to activate access.Before, every new member who joined required manual approval from the Owner, even in domains configured for auto-join. With this update, the flow became faster and safer:Auto-Join enabled: if the user’s email domain matches the allowed domains, they automatically join the workspace.Mandatory confirmation: the user receives an email invitation and must confirm it to become active.Security preserved: when the domain does not match or auto-join is disabled, it follows the traditional manual approval flow.This ensures a much faster onboarding experience without giving up email validation.Improvement in Default Message BehaviorWe adjusted how Kodus handles start and end review messages to reduce noise and keep the flow clearer, even when the user customizes the texts.Before, when editing messages, the behavior created extra messages instead of updating the existing one, especially in PRs with multiple commits. In addition, old start/end messages were not hidden in new reviews.Now the flow is consistent:Review start: sends a start message.Review end: updates the same message, indicating closure.New reviews: old start/end messages are automatically hidden.This ensures more clarity in the PR history, avoiding unnecessary duplications and keeping communication organized.Ignore IDE Rules in SyncIt is now possible to mark rule files that should not be synced by Kodus. Before, when closing a PR, all rule files (*.md, .mdc, etc.) were automatically synced, which was not always desired.With this improvement, the client can control what does or does not go into the sync flow:How it works: just add the tag @kody-ignored at the beginning or end of the file.Result: files with this tag are ignored in the process, preventing local or IDE-specific rules from being applied in the repository.This ensures more flexibility and avoids unnecessary noise in the team’s rulesBug FixesSuggestions already fixed were not automatically closedWe fixed the issue where Kody did not recognize suggestions implemented after a new push in already reviewed PRs. Now, when the client resolves the suggestion in the code, the corresponding comment is automatically closed.Limit of 35 subdirectories in folder selectorMonorepo support was limited to displaying only 35 subdirectories in the selector. This limit has been removed, ensuring that all necessary directories are correctly loaded.Duplication of users in Team ActivityWe resolved the bug that caused the Team Activity panel to show the same user duplicated in some scenarios. Now each user appears only once. September 9, 2025 1.0.51 – New review engine + rules library in packs 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. https://kodus.io/wp-content/uploads/2025/09/new-rules.mp4 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. https://kodus.io/wp-content/uploads/2025/09/pull-requests.mp4 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. August 29, 2025 1.0.47 Automatic Kody Rules + Review Flow Improvements 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. https://kodus.io/wp-content/uploads/2025/08/monorepo.mp4 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. https://kodus.io/wp-content/uploads/2025/08/monorepo-pasta.mp4 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 August 8, 2025 1.0.41 More context, less friction 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. https://kodus.io/wp-content/uploads/2025/08/filtro-1.mp4 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. https://kodus.io/wp-content/uploads/2025/08/preview-summary-Compressed-with-FlexClip-1.mp4 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. https://kodus.io/wp-content/uploads/2025/08/custom-mensagem-Compressed-with-FlexClip-1.mp4 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. https://kodus.io/wp-content/uploads/2025/08/logs-1.mp4 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. Privacy Policy Terms of Use support@kodus.io Meet Kody Home Pricing Security Knowledge Glossary Blog FAQ White Paper Benchmark Kodus vs Coderabbit Kodus vs BugBot Kodus vs Copilot Resources Docs Installation Changelog Support Our Network Linkedin X-twitter Reddit Github Discord @ 2026 Kodus. All rights reserved.