/devgenie:evidence is being built. It will be part of Lite. Until it arrives, running it shows a short message saying it is being built, with a link to this page. That message is all it does today: it calls no DevGenie service, runs nothing and writes no file.
This page describes how it is planned to work. The details may change before it arrives, and this page will be updated when it does.
What it will do
When Claude makes a claim about your repository, such as "this function is called from two places", it will be reminded to mark the claim with the file and lines it comes from. A local check will then look at the marked claims in each file write Claude makes:
- A write with a marked claim that cites a file Claude has not read in the current session will be refused.
- A write with a marked claim that cites lines that do not exist in the file will be refused.
- A write with no marked claims will be allowed, so a claim Claude does not mark is not checked.
When a write is refused, Claude is told why and can read the file and try again.
When to use it
When you want Claude's statements about your code to point at the code they come from, so that you can check them, and a marked claim that cites a file Claude has not read is caught before it lands in your files.
What it will change on your machine
It will add hook scripts to your project and the settings that run them, together with a short guide to the evidence rules. Each refusal will be added as one line to .devgenie/evidence-refusals.jsonl in your project: the time, the file, the check that refused it and whether the retry passed. No file content is kept in that list.
What it will send to DevGenie
Nothing from your project. The check runs on your machine and the list of refusals stays there.
How to switch it off
The command will explain the check and how to switch it off. How it is installed, switched off and removed will be described here when it arrives.