Independent by design
The value proposition is simple and memorable: one model writes, a different review surface critiques. That reduces self-confirming output.
Local-first AI review for serious codebases
Argus gives you an independent reviewer with structural maps, semantic search, git history, and diff-aware analysis, so the model reviewing the code is not the same one that just wrote it.
Why Argus
Most AI review workflows reuse the same shallow context that produced the patch. Argus takes the opposite stance: review should be independent, repository-aware, and composable enough to fit a real developer workflow.
The value proposition is simple and memorable: one model writes, a different review surface critiques. That reduces self-confirming output.
Structural maps, semantic search, git history, and cross-file analysis keep the review anchored in the actual codebase instead of just the diff.
Switch between OpenAI, Anthropic, and Gemini without changing the workflow. Gemini free tier keeps the first trial low-friction.
Repomap, difflens, codelens, gitpulse, review, feedback, describe, doctor, and MCP support can be used together or as Unix-style pieces.
Review surface
Argus is strongest when teams want more than a pass or fail. It gives the reviewer evidence about file relationships, history, and likely impact, so review comments can be specific instead of generic style feedback.
Use it locally before a pull request, in CI as a review gate, or through MCP when you want an IDE or agent workflow to call into the same review engine.
Install
Argus is published across Rust and npm surfaces. The fast path is to initialize config once and then pipe a diff into review.
npx argus-ai init
export GEMINI_API_KEY=your-key
git diff HEAD~1 | npx argus-ai review --repo .
cargo install argus-ai
argus init
git diff HEAD~1 | argus review --repo .