REPOSITORY ANALYSIS

jev-blindspot

A side panel for Claude Code and Codex CLI that shows the blind spots of each prompt you submit: what the request would have needed to consider and shows no sign of. Jev decides, in one call per prompt, whether the prompt is worth a second look; only then does the agent's own headless mode read the project and return the items. Nothing blocks the prompt, nothing is added to the session.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
2
Forks
0
License
MIT
Last commit
2026-09-22

What Jev does here

One gate call evaluates worth_checking, risk and possible gaps; local thresholds and duplicate suppression decide whether to start headless analysis.

Keeps the quick prompt gate separate from the deeper repository-reading agent and exposes why the panel remained quiet.

Fixed-version documentation and implementation material were inspected on 2026-10-24. No hooks, trust settings or headless agents were installed. Advice still depends on what the gate state and analysis agent can inspect.

What task does this project fit?

Decide when a submitted coding prompt merits a second, read-only inspection.

Material analysed:

From input to action

  1. A prompt, recent history and coarse repository facts form the gate state.
  2. Jev scores worth_checking, risk and possible gaps in one call.
  3. Local thresholds and duplicate suppression decide whether to launch the agent’s headless analysis.

Implementation details that matter

High risk changes the gate, not tool permissions

thresholds.ts chooses a different worth threshold for high-risk prompts and suppresses duplicates. The panel is advisory; its scores do not grant the coding agent additional authority.

Inspect the supporting source ↗

The transport has a bounded failure envelope

client.ts uses a hard timeout with SDK retries disabled and returns explicit no-key, timeout, HTTP or parse failures. Fake mode is a stub, not a live evaluation.

Inspect the supporting source ↗

When to choose it

Useful as a prompt-review side panel when deeper analysis is costly. It should not be installed or trusted as an approval gate for destructive commands.

How to inspect it yourself

Read gate/client.ts and thresholds.ts together. Follow a duplicated prompt to the quiet branch, then compare a low-worth result with the analyze branch. JEV_FAKE mode can check wiring only, not actual Jev quality.

Limits of this review

  • No hooks, trust settings or headless agents were installed.
  • Advice still depends on what the gate state and analysis agent can inspect.
Primary material used in this analysis