What it is
A streaming CLI for logs and text that filters lines by meaning instead of keywords. It works behind tail -f and kubectl logs -f, and is for anyone who needs to ask questions a regex cannot express.
How it uses Jev
Each line is judged by one Jev Noul: does `lines.line_NN` satisfy the user's question? Lines are batched into a state of named lines, and the returned probability of yes is compared to --threshold to decide whether to print the line.
Primitives:noul
Technique worth stealing
Naming each line in the state (lines.line_01) instead of using a list raised mean F1 from 0.76 to 0.91 for about 8% more tokens.
Try it
uv tool install jevgrep-cli && export OPENROUTER_API_KEY=sk-or-... then tail -f server.log | jevgrep "This line reports a real error, not routine noise"
Evidence
Each line is one question put to Jev about the README. ≥ 0.60 reads as yes, ≤ 0.40 as no; in between Jev is not making a call.
- Jev-centricyes0.89
- Shows a System One patternunclear0.50
- Handles uncertaintyunclear0.49
- Measuredyes0.87
- Runnableyes0.97
- Worth recommendingunclear0.52
- Model replicano0.04
- Problem scopescore on a 0–2 scale1.86
- About Jevyes0.98
Signals by Jev jev-1.13.0, card written by DeepSeek V4.1 Flash from the README on 21 Sept 2026.