Article
CommunityJev Benchmarks & Evaluations
Comparing Jev, Gemini, and OpenAI Decision Models
SlopCop blog post by Jonathan Ellis, published November 12, 2026, reporting a bakeoff of Jev against Gemini Decisions and OpenAI for classifying GitHub event relevance, the switch to GLiDE from Fastino Labs, and lessons on eval design.
- Format
- Article
- Reading time
- 2 min
- Published by
- Community
- Added
- Nov 2026
Highlights
- SlopCop ran a bakeoff of Jev, Gemini Decisions, and OpenAI for classifying GitHub event relevance.
- The team chose GLiDE from Fastino Labs for its revision, citing best results for its use case and low cost.
- GLiDE was the second-slowest service tested; Gemini and OpenAI most excelled on inference speed.
- Jev's recall looked like 0.91 against incumbent-derived labels but 0.57 against an independent panel.
- Relevant pairs were 11% of traffic, so the eval stratified on the incumbent's verdict and an independent Voyage reranker score.
Questions about this entry
Short answers drawn from the linked project or page.
It is a bakeoff of Jev, Google's Gemini Decisions, and OpenAI decision models for classifying whether GitHub events are relevant to a developer's work, written by Jonathan Ellis and published November 12, 2026.
They chose GLiDE from Fastino Labs for their revision, saying it gave the best results for their use case and was one of the cheapest options, with open-ish weights that require a separate commercial agreement above $10M annual revenue.
Against labels built from the incumbent's verdicts, Jev's recall looked like 0.91; against an independent panel it was 0.57. The post attributes the gap to truth filtered through the incumbent's answers flattering the incumbent.
GLiDE was the second-slowest service tested, while Gemini and OpenAI most excelled on inference speed. The post credits those vendors' massive hardware footprints and inference-speed expertise.
Relevant pairs were 11% of traffic, so a uniform sample would waste most labels on easy negatives. They stratified on the incumbent's verdict and on an independent Voyage reranker score, then weighted each pair by its stratum's size.
It says Jev is a good place to start when you lack the time or data for a proper eval, describing it as inexpensive, smart, and reasonably fast, while noting you can probably do better depending on your domain and priorities.
Recording why a pair is relevant, not only whether, showed that every model loses most of its recall on dependency items. That shifted the follow-up work from choosing a model to improving evidence.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.