Does this call Jev itself, and do I need an API key inside nvim?

No. The judging happens in the separate jev-lens Claude Code plugin; this one watches the verdict file it writes and draws it. There are no API calls and no key here, and nothing leaves nvim. You do need jev-lens installed in Claude Code first, or the popup has nothing to show.

How risky is stripping debris — will it delete code I wanted?

It deletes only what the verdict flagged, and it guards twice: it refuses outright if the buffer has unsaved changes, and it checks that every line still matches before deleting, behind a confirm showing the count. Those checks catch a drifted file, not a wrong judgement — the real risk is a flag that was never debris.

What are these unverified changes, and why do they break the quiet mode?

They come from jev-gates 0.4 or later, whose proof gate reports edits that could change behaviour where nothing ran, tested or checked afterwards. The number shown is Jev's probability that evidence exists, and each entry is a file row so the open key starts lazydiff on it. A behaviour change with no evidence is exactly the case worth interrupting you for, so it opens the popup even when every file looks routine.

Will it interrupt me while I am typing?

No. If you are in insert mode the popup waits until you leave it. The rest of the quiet rules: green is a single notify line rather than a popup, and verdicts where no file clears the bar, tiny diffs, all-cosmetic flags, the re-judge after a strip and repeats of files you just dismissed all stay silent. The same files will not pop again until something new joins.

How do I install the plugin?

Install jev-lens in Claude Code first, then add the lazy.nvim entry for rashedInt32/jev-lens.nvim with event VeryLazy. Neovim 0.10 or newer is all that is needed.

l opens the file with lazydiff, s strips the flagged debris after a confirm, r marks the verdict reviewed, j jumps to the Claude session, R judges again now, and q closes; the same files will not pop again until something new joins.

How does it find the verdict?

jev-lens writes ~/.claude/jev-lens/repos/ /verdict.json, keyed by the first 16 hex chars of the sha256 of your repo root. The plugin computes the same key, watches that folder and shows each verdict once, shared across nvim instances.

CommunityJev Integrations & Adapters

Jev Lens.nvim

Neovim popup that reads the verdict jev-lens writes after a Claude Code edit and tells you whether to open a diff, which files matter and why, with a strip-debris action, lazydiff on a key, and no API calls of its own.

See highlights

Open github.com

Stars: 1
Language: Lua
License: MIT
Published by: Community
Author: rashedInt32
Last verified: Oct 2026

rashedInt32/jev-lens.nvim

User repository on GitHub

View on GitHub

Neovim popup for jev-lens verdicts: do I need to look, which files, strip the debris

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

Claude Code just finished editing. Before you open a single diff, a popup tells you whether you need to look, which files, and why: The judging happens in jev-lens, a Claude Code plugin. This plugin just watches the verdict it writes and draws it. No API calls, no key, nothing leaves nvim. l opens the file and turns on lazydiff if you have it, so you land on the change.

Quoted from the project's README. Read the full README.

Tagscommunity awesomejev catalog-import lua

Works forJev for Classification

Used inJev for Software & DevTools

Highlights

Draws a verdict another tool produced: it reads the verdict file under ~/.claude/jev-lens and makes no API calls, needs no key and sends nothing out.
The strip key removes flagged debris after a confirm that shows the count, refusing on unsaved changes and re-checking every line first.
With jev-gates 0.4 or later, changes that could alter behaviour but had nothing run, tested or checked open the popup on their own.
Quiet by design: green is one notify line, and tiny diffs, all-cosmetic flags, post-strip re-judges and repeats of dismissed files stay silent.

Watch out

This is a viewer, not a judge: jev-lens must already be installed in Claude Code and does the API work, so installing the plugin alone leaves you with nothing to show. lazydiff is optional and only changes what the open key does. The strip action is the one thing that edits your buffer — it refuses when there are unsaved changes and verifies each line still matches, but a flag that was wrong in the first place would still delete code. With jev-gates absent the unverified-changes section simply does not appear, and shadow-mode verdicts stay hidden by default. Neovim 0.10 or newer is required. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

jev-edge

Gateway-side admission control judging incoming requests with a typed decision model, layering cheap rules, synchronous judgment, and an async side path that never blocks responses.