Review comments, commit statuses, force-push detection, and webhook coverage now work consistently for Forgejo repositories. If you self-host with Forgejo, Kody behaves just like on any other major platform.
Eliminated duplicate API calls when syncing Kody Rules from changed files. PRs with many files now close noticeably faster.
Platform settings that don’t apply to your current Git provider, such as GitHub-specific options when you’re on GitLab, are now hidden automatically. Less clutter, fewer misconfigurations.
Reconnecting a Git provider after disconnecting: previously, disconnecting a provider left stale integration configs behind, causing reconnects to fail. Now stale rows are properly cleaned up.
Kody conversation replies with empty responses: resolved an issue where Kody occasionally replied with blank content in PR comment threads when using Claude Sonnet.
NaN deduplication indices: added three-layer protection against NaN values appearing in suggestion deduplication indices, preventing rare but confusing duplicate suggestions.
Forgejo prompt field always empty: the formatPromptForLLM function was reading a non-existent field on Forgejo PRs, causing the prompt section to be blank. Now it reads the correct field.
Self-hosted AST graph reliability: the kodus-graph CLI was installed but not available to the runtime user in self-hosted worker images. Fixed PATH and install order so graph indexing works out of the box.
Orphaned agent trace records: prevented a race condition in chunked review mode that could leave orphaned IN_PROGRESS trace records in the database.
Platform settings not scoped to Git tool: settings incompatible with your current Git provider were still visible. Now they’re properly filtered based on the connected tool.
No changelog entries for this filter yet.
Track the health of your review pipeline in real time. Throughput, queue, and processing time metrics are now available in Cockpit.
The review tab has been redesigned with a cleaner interface and more direct actions. You can now analyze and act on suggestions without leaving the PR screen.
We migrated the backend from Yarn 1 to pnpm. This makes builds faster, improves lockfile consistency, and reduces cache issues across environments.
The token usage screen has been redesigned to make consumption by organization and period easier to understand. It is now simpler to track usage and see how tokens are being consumed over time.
Self-hosted analytics: we fixed the analytics integration for self-hosted deployments. Usage metrics now appear correctly in the dashboard.
Issue cache: the issue count in the sidebar could sometimes become outdated. The cache is now invalidated correctly after changes.
GitHub rate limit: we fixed a rate limit issue in cloud E2E tests. We now use round-robin across multiple bot accounts to better distribute requests.
Notification routing: we fixed the behavior of targeted notifications when combined with audience settings. Notifications now reach the right people without duplicates.
Centralized config sync: we fixed issues in the centralized sync of Kody Rules configurations across repositories. Sync now correctly handles multiple scopes, stale configurations, and merge-triggered updates.
No changelog entries for this filter yet.
We added support for Moonshot as a provider, compatible with the Anthropic API.
You can now use the Kimi Coding Plan model in BYOK setups. To configure it, set the API_MOONSHOT_API_KEY key and select the model in the organization preferences.
See the Moonshot (Kimi) documentation for more setup details.
Organizations can now set monthly token consumption limits per model.
Usage is shown in real time in the interface, with a progress bar. When usage reaches 80% of the limit, the team receives an email alert. If the limit is reached, additional reviews can be blocked automatically.
See the Monthly Spend Limit documentation for more setup details.
The review engine now handles empty or malformed LLM responses better.
This reduces loops in edge cases and helps ensure valid suggestions continue to be delivered even when the provider returns an unexpected response.
On-premise installations now automatically report health metrics, such as heartbeat, and usage data.
The goal is to make diagnosis and support easier without exposing sensitive customer data.
We improved the loading and synchronization of custom rules.
We also fixed the count of orphaned rules and made partial updates safer against race conditions.
- Support for GitLab 13.x in comment webhooks
- Diff fallback for versions earlier than 15.7
- Fixes for discussion threads and replies scoped by discussionId
- Self-hosted development environment documentation
GitHub: suspended users no longer appear in the member list for license assignment.
Update Connection: integration reauthentication now correctly clears the previous configuration.
Integration reset: Kody Rules linked to the repo/directory are now removed automatically.
Release Freeze: eligibility notifications only appear when the freeze is active.
No changelog entries for this filter yet.