# Claude Code — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/claude-code

An agent can discover context through targeted search and reads.

## What we admire

Claude Code’s tool-driven workflow helped normalize a coding agent that explores the repository, edits files, and runs checks in one loop. Its review workflow also provides a clear comparison for AI-first review.

## The principle that stayed

The path from task to change is observable, but an agent’s own confidence is not a verdict. Independent, executable checks and explicit coverage are needed before calling the task complete.

## Where CodeVetter stands

CodeVetter can work with an installed Claude CLI and can evaluate its changes. It stores per-run evidence and does not treat a Claude review as independent proof of correctness.

## Sources

- [Claude Code overview](https://code.claude.com/docs/en/overview) — the creator's own source
- [CodeVetter project log](https://github.com/Codevetter/codevetter/blob/main/docs/archive/project-log.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

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