Overview and system requirements
What Kensa does, how the desktop app and the website fit together, and what you need before installing.
Kensa is a desktop app that reviews pull requests and local changes with specialist AI agents while you stay in control of every decision. This page explains what Kensa does, what runs where, and what you need before installing it.
What Kensa does
- Reviews pull requests and local diffs with specialist agents — architecture, security, error handling, testing, and code quality — and presents structured findings on one review surface.
- Runs every review on your machine through the agent CLI you configure (such as Claude Code, Codex, or Gemini CLI). Kensa does not run reviews in the cloud.
- Attributes every finding to the agent, provider, and model that produced it, so you can judge how much confidence to place in it. Providers differ in capability and cost.
- Keeps Git provider tokens in your OS keychain and review results in local app storage.
Desktop app vs. website
| Kensa desktop app | Kensa website | |
|---|---|---|
| Purpose | Review engine and main workspace | Download, documentation, account |
| Runs reviews | Yes — locally, through your own agent CLI | No |
| Needs an account | Yes — sign-in is required | Only for the account pages |
The signed-in web panel is a minimal shell today. These guides document the desktop app.
System requirements
| Requirement | Details |
|---|---|
| Operating system | macOS (Apple silicon or Intel). Windows and Linux builds appear on the download page when verified. No minimum OS version is asserted. |
| Git | Installed and on your PATH — used for clones, diffs, and worktrees |
| Agent CLI | At least one supported agent CLI; the setup wizard lists them with install hints |
| Git provider | A GitHub, GitLab, Bitbucket, or Azure DevOps account to connect — or the gh CLI as a legacy GitHub path |
| Local clone | Required for Deep Review, Source Control, and worktrees; not required for Quick Review |
Agent CLIs and Git providers are third-party services with their own accounts and terms; Kensa uses them under your credentials, from your machine.
Next step
Install Kensa — download a verified build and complete first-run setup.