Introduction
What is Verity?
Verity is independent verification for coding agents: a quality gate, a shared memory, and cost visibility for every agent working in your repositories. Built by Codacy.
Coding agents are fast and they are unsupervised. Verity is the peer that watches the work. When an agent finishes a change — or is about to commit or push one — a model that did not write the code, backed by deterministic static analysis, reviews it against your project's Standard and returns PASS, WARN or FAIL with file-and-line findings. A blocking finding goes back to the agent to fix, up to a limit. What the review learns is written to a knowledge base the next agent reads before it starts. And every token your agents spend is metered in one place.
The gate
A model that did not write the code reviews every change — after each turn, and before a commit or push lands.
Memory
A Markdown knowledge base in your repo that every agent reads before it starts and adds to when it finishes.
Cost
What every agent spent — by model, session, run and repository — in one place.
How it fits into your work
Verity runs as hooks inside Claude Code. There is no extra step per change: you and your agent work the way you already do, and Verity attaches to the moments you choose — after every agent turn, before a commit, before a push. The review runs out-of-band, in its own context window, so it never spends your agent's tokens. Everything it decides is recorded to a dashboard at verity.md, where the same GitHub login the CLI uses shows you every session, run, task and dollar across every repository you can read.
Three things Verity is deliberately not: it is not a linter — a security scanner (Trivy) gives it evidence, and it adds an independent judge and an intent check on top; it is not a git hook or a CI job — the commit and push gates fire on the agent's git commands inside Claude Code; and it does not keep your code — the diff is reviewed in memory and discarded, and only findings, scores and decisions persist (Security & privacy).
Requirements and availability
- macOS or Windows. Linux is not supported yet.
- Node.js 20+ and git.
- Claude Code. Verity is installed as Claude Code skills and hooks. Support for other harnesses is coming; see the compatibility strip below for what is live today.
- A GitHub account to sign in. Sign-in is optional — without it the gate still runs locally, but nothing is recorded — and other providers are not supported yet.
- A Free plan, with no credit card. Pro and Fleet have higher limits (see pricing).
Install
In Claude Code, as a plugin — it carries the CLI, so there is nothing else to install:
/plugin marketplace add codacy/verity/plugin install verity@verityOr as a global CLI, which is also what CI uses:
npm install -g @codacy/verity-cli && verity initWorks with
verity init signs you in through GitHub, wires the hooks and writes your Standard — your team's if the repository already has one on Verity, built from the review packs that fit your codebase if not. One sign-in covers every repository you can write to. Under two minutes; the Quickstart walks through it.
Find your way
| I want to… | Read |
|---|---|
| Install it and see a first verdict | Quickstart |
| Understand what happens on each turn | How it works |
| Review at commit and push, not every turn | Moments |
| Find races and double effects a review cannot see | Formal verification |
| Verity blocked something — what now? | Findings & verdicts |
| Change what it enforces | The Standard |
| Onboard a teammate, or set up CI | Authentication |
| See what it recorded | The dashboard |
| Know what leaves your machine | Security & privacy |
| Know what a file in .verity/ is for | Files & configuration |
The CLI & commands page is the full reference, and Troubleshooting is organized by symptom. What changed recently is on the changelog.