Skip to main content
GitHub.com only. GitHub Enterprise Server, GitLab and Bitbucket are not supported, and neither are SSO or an audit log.
It reviews any text source file that is not on the skip list. It is tested and measured on Elixir, Ruby and Rails, TypeScript and React, Python, and Go: known defects are planted in code in those languages and we check how many CodeWarden finds. Other languages are reviewed by the same model, without that measurement behind them.The comments themselves can be written in any language you set with language.
No. It reads the diff, the changed files and a few related files through the GitHub API. Nothing is cloned, and nothing from your repository is ever executed: no build, no tests, no linters.
No. A dependency graph needs the whole repository, which means a clone. Instead, CodeWarden finds the files that use the code a pull request changed with GitHub’s code search, inside your repository, and shows up to three of them to the model, read from the base branch. Rules that no graph could find belong in .codewarden.yml.
No. Every review is posted as a comment review. It never approves and never requests changes, so it cannot block a merge.
Usually because the push added nothing new to review, or the follow-up review found nothing: a later review with nothing to say posts nothing. Other reasons: the pull request is a draft (skipped by default, and not listed in the console), the repository is switched off, .codewarden.yml skips it, the allowance is used up, or there is no subscription. The repository’s page in the console shows each review with its status.
By design. A review publishes only findings with a confidence of at least 0.7, at most 8 comments by default, and never style remarks. The console lists every finding it dropped and why.
No. Which model reviews a pull request is CodeWarden’s responsibility, and a model we have not measured would give a review we cannot vouch for.
No. A push that touches nothing new calls no model and uses no AI turn.
Not by default. A draft is reviewed when it is marked ready for review. To review drafts too, set skip.drafts: false in .codewarden.yml on the base branch.
No. Review rules live in .codewarden.yml in your repository, read from the base branch. The console decides which repositories are on, who can see them, and what is paid for.
No. Only people with write access to the repository, and the pull request’s author, can get an answer to a mention. Anyone else is ignored at no cost.
No. .codewarden.yml is read from the base branch, so editing it in a pull request does not affect that pull request’s review. Text in the pull request that tells the reviewer to approve or stay quiet is treated as data, not as instructions.
The privacy policy answers this in its section “Who else sees it”: every request to OpenRouter asks it to use only providers with a zero-data-retention policy that do not store or train on what they receive.