Skip to main content

​
Kody Code Review Not Working? Steps to Fix Common Issues

​
Token Issues

If you’re connected via a token, ensure these points are checked:
  • GitHub Users: Verify that your token is enabled for your organization:
    1. You must be the organization owner.
    2. Go to your organization’s settings in GitHub:
      • Use the following URL and replace YOUR_ORG_NAME with the name of your organization: .
    3. Under Fine-Grained Personal Access Tokens, ensure “Allow access via fine-grained personal access tokens” is selected.
  • Personal Access Token (PAT): Confirm that your token is configured for your organization and has the required permissions. Manage tokens.
  • Token Expiry: Make sure your token is active. Check token status.
Token Example

Your token should display your organization's logo. If it shows your personal profile picture, your token is set to personal access instead of organizational access.

​
Configuration Issues

  • Automated Reviews: Ensure Enable Automated Code Review is on in Code review → General at the Global scope (open). If disabled, start reviews manually with @kody start-review.
  • Review Categories: Ensure at least one category (Bug, Performance, Security, Business Logic) is turned on for Kody to provide suggestions, and check the Minimum severity to post. Both live in Code review → What to review (open).
  • Branch Reviews: By default, Kody reviews PRs merged into the default branch. To include additional branches, update Base Branches in Code review → General (open).
  • Large PRs: Be aware that PRs with a high number of changes may take longer to process.

​
Global vs. Repository Settings

Kody uses a hierarchical configuration system. Here’s how it works:
  • Global Settings: Applied to all repositories by default.
  • Repository-Specific Settings: If configured, they will override global settings for that specific repository.

​
Steps to Troubleshoot

  1. Check Global Configuration: Review and confirm global settings are correct. Access Global Settings.
  2. Verify Repository Settings:
    • Open the scope picker at the top of the Code review group in the sidebar. Repositories (and directories) with their own configuration are listed under Global.
    • Confirm if custom configurations are set for the repository in question.
    • Also check that the repository is selected for review on the Repositories page (sidebar → Repositories).
  3. Align or Clear Configurations:
    • To apply global settings, clear any repository-specific configurations (the repository’s ⋯ menu in the scope picker → Delete configuration).
    • Alternatively, adjust the repository-specific settings to meet your needs.

​
Common Symptoms

  • Automated reviews are not triggered for a repository.
  • Kody applies unexpected settings or suggestions.
  • Global settings are not reflected in specific repositories.

​
No Response or No Comments from Kody

Work through this quick checklist:
  1. PR contains reviewable code changes (not only docs or images)? Kody may skip if there’s nothing relevant to analyze.
  2. Branch is in scope? By default, only PRs targeting the default branch are reviewed unless additional base branches are configured.
  3. Large PRs: Kody reviews PRs with up to 2,000 reviewable files (after applying Ignored files). Example: PR with 2,500 total files but 600 are .lock files → Kody reviews the remaining 1,900 files ✅
  4. Mode: If automated reviews are disabled, trigger manually with @kody start-review.
  5. Push cadence: If using auto-pause, wait for the cool-down or request a manual review.
  6. Repository overrides: Repo-specific settings can override global ones. Clear or align them as needed.

Review Modes & Cadence

Check automated review, cadence, and branch filters.

Limits & Pricing

Learn about suggested limits and how they affect reviews.