# CodeVetter FAQ

> Canonical page: https://codevetter.com/faq

## What is CodeVetter?

CodeVetter is an execution-backed verification and evaluation system for coding agents. Its core loop is task, agent change, executable verification, evidence, and a measurable verdict. CLI, MCP, and machine-readable verification bundles are primary product surfaces; the desktop app is a local viewer.

## Does CodeVetter upload repositories to its own server?

No. CodeVetter has no hosted review backend. Repository context, review history, and product state remain on the local machine. When a user explicitly invokes an external model provider, that provider receives the request under its own policy.

## Which coding agents and model providers can it work with?

The desktop work surface can supervise installed Codex and Claude CLIs. Review supports user-configured Anthropic, OpenAI, and OpenRouter providers. Provider availability and account policy remain external to CodeVetter.

## What evidence does a review retain?

Findings can retain source anchors, command or test evidence, verification state, and portable proof exports. Missing, waived, stale, and unverified stages stay explicit rather than being presented as successful.

## Is there a public benchmark?

Yes. The public synthetic benchmark contains 27 hand-labeled cases and 29 expected findings. Its cases, labels, reviewer outputs, and scorer are published so the result can be reproduced.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)