Categories
Each category has a switch. All four are on by default.
A finding in a category you turned off is not posted. Kody Rules and custom agents are not categories; they run whatever the switches say.
Business Logic needs a connected task tracker. Click its row to open its settings. See Business Logic Validation.
Instructions per category
On the Bug, Performance and Security rows, Instructions opens an editor showing what Kody looks for in that category. Edit it to match your codebase. See Instructions & Personality.Coding-agent instructions
Coding-agent instructions (off by default) lets Kody read files such asCLAUDE.md, AGENTS.md and .cursor/rules and point out changes that break them. See Coding-Agent Instructions.
Kody reads these files through the Bug, Security and Performance reviews, so the setting needs at least one of them on.
Minimum severity to post
Kody posts only findings at or above this level. Apply the threshold to Kody Rules extends it to your rules. See Severity Threshold.Custom agents
When custom agents are enabled for your workspace, they are listed under the categories. See Custom Agents.Deterministic checks
Deterministic checks scan changed files for vulnerable dependencies and exposed credentials, and can use CI results as evidence. Beta The section appears on Cloud when the workspace has access to deterministic checks. On self-hosted, setBETA_FEATURES=true. Each check starts off.
- Vulnerable dependencies — checks packages a pull request adds or bumps against public advisory databases, and reports only the vulnerabilities that change introduces. It reads lockfiles even when they are on the ignored files list.
- Committed credentials — scans changed files for tokens, keys and private keys.
- Use your CI’s results as evidence — reads the checks already on the commit. Nothing is re-run. On GitHub this needs the Kodus app: a personal access token cannot read check runs.