Claude Code, Cursor and Copilot plan from the context files in your repo. Every merged PR widens the gap between what they say and what the code does.
Proposed on a branch you review
Every other line in the file stays byte-identical.
Every claim lands in one of three states
Commands are matched to your manifests, paths to your file tree. No model decides what is true: an anchor resolves or it does not.
The audit runs on its own and costs nothing. The correction is the part you ask for.
Install the GitHub App or add your GitLab project. The first audit runs in about a minute and tells you what your context files get wrong today: every command and path they claim, resolved against the code at HEAD.
Nothing to add to your pipeline. Kontrua posts a kontrua/context commit status and one comment naming each broken claim with its file, line and reason. A claim it cannot decide is reported, never failed, so the check stays worth requiring.
The correction lane opens a pull request that repairs the drifted lines: the context artifacts Kontrua owns, plus single-line corrections to the files you wrote. You review it like any other PR. This is the part that is metered.
The audit needs no trigger: every push and every PR gets its verdict, free. These are the ways to launch a correction, the run that rewrites what broke.
Install the GitHub App or connect your GitLab project. Kontrua audits every pull request for free, and when the repository is set to trigger on approval it runs the correction for the claims that pull request broke.
Trigger mode is per repository: on PR approval, on merge, or manual only.
Nothing to paste
Kontrua receives the pull request event from the GitHub App or your GitLab project, so both the audit and the correction start without a snippet in your repository.
Hand-maintained context vs. Kontrua.
Audits and PR verdicts are unlimited on every plan: connect a repo, push, open a pull request, get a verdict on every claim. The allowance counts corrections only, and one run is one correction pass. The API trigger and the Notion sync work on every plan; scheduling needs a paid one. Open-source repos always get Max features, free.
For solo devs and small projects
or $24 per developer per month, billed annually
For growing engineering teams
or $48 per developer per month, billed annually
For teams shipping at scale
Custom solutions for your team
The context files agents read before they plan: AGENTS.md, your conventions, your docs. Every command and path they claim is resolved against the real code, on every push and every pull request.
No. Commands are matched against your manifests and paths against the file tree. A claim is verified, broken, or reported as unverifiable. No model sits in the verdict path, so the verdict cannot hallucinate.
It corrects them. When the audit finds a broken claim, the correction lane can open a pull request that rewrites only the false lines, and you review it like any other PR. Kontrua does not invent documents from scratch, and never ships a sentence it cannot anchor to the code.
No. Your file is the asset. A correction edits only the lines the code made false; everything else stays byte-identical.
Any tool that reads context files from your repo: Claude Code, Cursor, Copilot, and anything else following the AGENTS.md convention. Standard files, no SDK, no lock-in.
Audits and PR verdicts are free and unlimited on every plan, including Free. You pay per developer for corrections, the runs that rewrite what broke.
Kontrua never stores your source. Diffs and file contents are analyzed in memory during a run and discarded. Writes only ever land on a Kontrua branch, never on your default branch.
Connect a repo. The first audit takes about a minute, costs nothing, and every claim gets a verdict.