Here is the tl;dr ELI5.
Think AI multiple choice, not AI essay writing.
It doesn't chat. It makes decisions your software can act on: "Spam or not?" "Which tool should this agent use?" "Does this need a human?"
The exciting part: roughly 200x faster and 400x cheaper than frontier LLMs in TypeSafe's own workflow benchmarks, with responses in a fraction of a second.
Why that's powerful: imagine an app or agent making hundreds of little judgment calls without hundreds of expensive, slow conversations with an LLM.
Keep the big model for the hard thinking and writing. Use Jev for the rapid-fire decisions in between.
Oh, and it is casually made by Diogo Almeida, co-creator of ChatGPT and one of the co-inventors of RLHF, who spent two years in stealth on it.
That is the pitch. Here is what the receipts say.
Nine /last30days sweeps, every raw file read in full, and every big post checked by hand against the live page. The launch post is sitting at 66K likes and 31.4M views two days in.
https://x.com/CompleteSkeptic/status/2099925682726002904
A browser agent built on it did 1.8M views in a day. And one developer counted his bill: about 5,000 requests for roughly two dollars, spread across classification, model routing, intent and steering.
https://x.com/MichaelLee04/status/2100003037150683593
I did not run these workflows. I pointed the research at the community and ranked what people are actually shipping. Out of 31 candidate workflows with a named source and a real number, these are the 9 worth stealing, each with the payload to copy.
🧠 The mechanics, in sixty seconds
You hand it your app's state plus a typed question, and it hands back a typed decision with a probability attached. No JSON prompting, no parsing layer, nothing to validate.
Three question types, and that is the whole surface: \Choice\ picks one of up to 255 options, \Score\ places something on a scale, \Noul\ answers a yes or no as a number from 0 to 1. Every answer carries \probabilities\ and a \confidence\ score. Ask twenty questions about the same state in one call and they evaluate in parallel, so twenty costs about what one does. Input is $0.042 per million tokens. Output is free.
The community landed on the same framing as my tweet, with a lot more reach: LLMs generate answers, Jev makes decisions, 2,278 likes.
My headline numbers come with a footnote. TypeSafe puts response time at 70 to 500 milliseconds and 40x to 200x faster than frontier models. The exact pair on their home page, from their own workflow evals, is 193.6x faster and 444.6x cheaper. The baseline it is measured against matters:
So, here's their homepage, and the first thing they hit you with is the side-by-side against GPT-5 X Terra, one of OpenAI's mid models.
- Nimrod, YouTube, 13,747 views
The name is not a Kahneman reference, even though the model class is called System One.
Here's where the name Jev actually comes from, and it's not Kahneman, it's a 19th-century economist named William Stanley Jevons.
- Dots and Arrows, YouTube, 14,597 views
Jevons paradox: make a resource cheaper and people consume far more of it. Naming your decision model after that is a thesis statement.
It is also a bit. Rob Shocks cut to a "My name is Jeff" clip in his 231,655-view breakdown and the top comment, 142 likes, was just "My name is Jev killed me." Diogo has been fielding the jokes himself, 129 likes.
1. 🌐 A browser agent that finds flights in 7 seconds for $0.0039
What it is. A tiny open source browser agent where Jev picks the next click and a small LLM only wakes up when something needs typing.
Who runs it. Gregor Zunic, the Browser Use founder. 7.2K likes, 1.8M views, 7.6K bookmarks. He notes in the post that the video runs at 1x speed.
https://x.com/gregpr07/status/2100411066966749359
Why it earned a slot. It is the single most-watched thing anyone has built on the model, and it is the cleanest illustration of the pattern that keeps winning: a new action space every step, the DOM as the state, Jev choosing among the candidates, generation only as a fallback. LangChain's own writeup says Kyle Jeong at Browserbase is doing the same thing for fractions of a cent.
The payload is the repo: browser-use/jev-ultrafast. Clone it before you write your own.
2. 🧹 Instant compaction: score every tool call and drop the junk
What it is. Replace the summarization prompt that every coding agent runs at the context ceiling with a Jev pass that scores each tool call for relevance and deletes the dead weight.
Who runs it. Tamara Tran asked the question and shipped the answer the same afternoon. 5K likes, 554.4K views.
https://x.com/tamarajtran/status/2100694549362553153
Alex Volkov ran it as a Claude plugin and posted the number: one second to take a session from nearly 1M tokens to 86K. 1.9K likes, 3.5K bookmarks.
https://x.com/altryne/status/2100739055923425589
Why it earned a slot. Because Diogo's reply is the tell about where this goes. 304 likes.
https://x.com/CompleteSkeptic/status/2100702845779775675
If a harness can score and drop in one second instead of summarizing, the context window stops being the thing you design around. This is the sleeper pick. Browser Use is better on video; compaction is the one every coding-agent user feels today.
Paste this into Claude Code, which is Alex's exact install line:
1Install, and configure: https://github.com/tamaratran/fast-jev-compaction
3. 🛡️ The safety reviewer, unbundled from the harness
What it is. Every coding harness runs a classifier that asks "should this command execute?" before auto mode lets it. Until this week that classifier lived in the closed part of the product.
Who runs it. Vercel, in production. Guillermo Rauch: the default mode in fx is auto, with a safety reviewer analyzing every command, and Jev is up to 18x faster at p95 and more accurate than the model running it today. 3.7K likes, 392.4K views.
https://x.com/rauchg/status/2100307962262872105
https://x.com/fazxes/status/2100300097695232164
Why it earned a slot. Because it is a production migration with a p95 number attached, and because LangChain shipped the open version the next day as \AutoModeMiddleware\. The Rob Shocks breakdown, 231,655 views and 3,526 likes, is the one to send to a teammate who wants the story in ten minutes.
The LangChain version, verbatim from their post:
1from langchain.agents import create_agent2from langchain_typesafe.experimental.middleware import (3 AutoModeMiddleware,4)56guardrail = AutoModeMiddleware(tools=["bash"])78agent = create_agent("openai:gpt-5.6-luna", middleware=[guardrail])
4. 🚦 Model routing as a middleware, not a system prompt
What it is. Put Jev in front of your model fleet and let it pick which brain handles each request, with the probabilities left in agent state so you can audit the choice.
Who runs it. LangChain, in Sydney Runkle's "Building a Harness with Jev." 232 likes, 31.1K views, and the cleanest how-to-wire-it piece anyone has published.
https://x.com/sydneyrunkle/status/2100754364545761643
Why it earned a slot. Model routing is the most-cited job for the model in the whole corpus; it is one of the five workloads in the 5,000-requests-for-$2 post at the top of this article. LangChain turned it from a paragraph in a system prompt into eleven lines you can read.
1from langchain.agents import create_agent2from langchain_typesafe.experimental.middleware import (3 ModelChoice,4 ModelRouterMiddleware,5)67router = ModelRouterMiddleware(8 choices={9 "fast": ModelChoice(10 model="openai:luna",11 criteria="Direct lookups, extraction, and localized changes.",12 ),13 "powerful": ModelChoice(14 model="openai:sol",15 criteria="Architecture and high-stakes decisions.",16 ),17 },18 instructions="Choose the least costly model that can complete the task.",19)2021agent = create_agent("openai:gpt-5.6-luna", middleware=[router])
Install with \pip install langchain-typesafe\ and set \TYPESAFE_API_KEY\.
5. 🔎 RAG precision: retrieve as usual, then delete what does not belong
What it is. Keep your retriever exactly as it is. Run Jev over every chunk it returns with one yes-or-no question, and drop the ones that fail.
Who runs it. Kush Bhuwalka put it in one sentence: run Jev on all the chunks it retrieves and delete the irrelevant ones. 416 likes.
https://x.com/kushbhuwalka/status/2100731050075050485
Why it earned a slot. Precision has been the unsolved half of RAG because the fix was always another LLM call per chunk, which nobody could afford at retrieval time. At free output tokens and sub-second latency, a per-chunk verdict is cheaper than the embedding lookup that produced the chunk. This one I wrote against the documented API, in the shape Kush described:
1from typesafe_sdk import Noul, TypeSafeClient23client = TypeSafeClient()45kept = []6for chunk in retrieved_chunks:7 verdict = client.system_one(8 state={"question": user_question, "chunk": chunk.text},9 questions={10 "relevant": Noul(11 instructions="The chunk contains information needed to answer the question",12 ),13 },14 )15 if verdict.answers["relevant"].noul > 0.5:16 kept.append(chunk)
6. 🎮 Real-time loops: Minecraft, Doom, and a launcher that reads your mind
What it is. Decisions inside a loop that runs many times per second, where a frontier model cannot participate at all.
Who runs it. Wuyang Zhou has Jev and GPT-6 Astra playing Minecraft together, Jev on the quick reactions and Astra planning ahead, fighting multiple zombies at once. 374 likes, 51.4K views.
https://x.com/wuyang_zhou/status/2100727660875808913
Nader Dabit built a keystroke oracle: type "the pdf I just downloaded" and the newest PDF is already the top hit, with full confidence, on every keystroke, in about 100 milliseconds. 264 likes.
Why it earned a slot. TypeSafe's own launch demo is Doom, with the model asked what to do about ten times a second. Two independent explainers worked out the same cost for that loop:
Jev's playing in real time around 10 decisions a second, and that works out to about $7 an hour.
- AI WITH Rithesh, YouTube, 19,904 views
Ten decisions a second for seven dollars an hour puts it in a different category from an LLM, and the Minecraft split, fast model reacts while slow model plans, is the pattern every real-time pick in this list shares.
7. 📬 Email triage at batch scale
What it is. Point Jev at an inbox export and have it sort, score and flag every message in parallel.
Who runs it. The vogel channel on YouTube, 60,996 views and 526 likes, ran 1,500 exported emails in batches of 100 with 8 workers. LangChain's writeup names Ryan Vogel as one of three projects it is watching. Syntax, 33,933 views and 1,052 likes, built the same thing plus a home automation demo that goes from question to API call in 300 milliseconds.
Why it earned a slot. It is the most-copied demo in the corpus, and the throughput math is the point.
We only have a balance of $5 down here, which just shows how cheap this model is.
- vogel, YouTube, 60,996 views
This is TypeSafe's own quickstart, verbatim, and it is already an email triage pipeline:
1pip install typesafe-sdk
1from typesafe_sdk import Choice, Noul, Score, TypeSafeClient23client = TypeSafeClient()45response = client.system_one(6 state="Hi, I've been trying to connect my Stripe account for 3 days and it keeps failing. I'm losing sales. Please help ASAP.",7 questions={8 "department": Choice(9 instructions="Which team should handle this",10 criteria={11 "billing": "Payment or subscription issues",12 "technical": "Bugs or integration problems",13 "sales": "Pricing or account questions",14 },15 ),16 "frustration": Score(17 instructions="How frustrated the customer appears",18 criteria=[19 "Calm, just stating facts",20 "Frustrated but civil",21 "Very angry, strong language",22 ],23 ),24 "is_urgent": Noul(25 instructions="The message conveys urgency or time-sensitivity",26 ),27 },28)2930print(response.answers["department"].choice)31print(response.answers["frustration"].score)32print(response.answers["is_urgent"].noul)
8. 🗂️ Map-reduce over documents: 777 judgments for a quarter of a cent
What it is. One set of questions, every document, all at once. The workload that has been economically impossible with frontier models and mediocre with classical classifiers.
Who runs it. Mike Taylor, head of evals at Every, ran the cleanest test anyone has published: 27 of his own articles plus 10 AI-styled counterparts, 21 questions each, all in one request. 777 judgments in less than 0.7 seconds, for about a quarter of a cent. Across all eleven of his experiments, 1,709 judgments for under a cent. The AI Daily Brief, 10,000 views, picked the number up the same day.
Why it earned a slot. TypeSafe lists this as a first-party category, "AI Map Reduce over Big Data," on their use-case map. Free output tokens change the arithmetic on anything you run per row. The raw HTTP shape, from the docs, is small enough to fit here:
1{2 "model": "jev-latest",3 "state": "Hi, I've been trying to connect my Stripe account for 3 days and it keeps failing. I'm losing sales. Please help ASAP.",4 "questions": {5 "is_urgent": {6 "type": "noul",7 "instructions": "The message conveys urgency or time-sensitivity"8 }9 }10}
That returns \{"is_urgent": {"type": "noul", "noul": 0.999}}\. Twenty questions in the \questions\ object cost about what one does, so ask everything you want to know per row in a single call.
9. 🧪 Jev in your browser, and the clones
What it is. The interface, reimplemented on top of a local model by people who wanted the shape without the dependency.
Who runs it. Kshetrajna Raghavan at Shopify built Reflex, a Qwen model running structured decisions with probabilities on WebGPU, entirely in the browser. Tobi Lütke passed it around: 206 likes, 38.5K views.
https://x.com/tobi/status/2100742327459303882
A reverse-engineered jevlike pulled 157 points on the Hacker News front page two days after launch, and mini-jev, the same interface on a local LLM, followed a day later. The community catalog, awesome-jev-by-typesafe, was at 409 stars when I pulled.
Why it earned a slot. Three independent clones inside 72 hours is the strongest signal in this sweep about whether the interface is the real invention. It also gives you an offline escape hatch for anything you cannot send over the wire, which matters because the real thing is API-only and US-hosted. Try Reflex in a tab right now.
📖 How TypeSafe says to use it
Four rules, from the docs and from the founder's own replies:
- Ask many questions per call. They evaluate in parallel, and the docs say extra questions barely change response time. Every pick above that impressed anyone was asking several things about one state.
- Threshold on confidence. The docs tell you to treat anything under 0.3 to 0.5 as a signal to ask a human rather than act. This is the difference between a classifier, which hands you a label, and a decision system, which hands you a label plus permission to use it.
- Give it candidates, do not ask it to invent. Browser Use builds the action space from the DOM and Jev picks. RAG retrieves and Jev filters. The launcher ranks and Jev re-ranks. Choice supports up to 255 options; add an "other" for the edge cases.
- Get the grading right or nothing else matters. One builder who spent the week trying to break it put it plainly: "if you don't get the grading right, it doesn't work." The option set and the question wording are the work; the call itself is trivial.
Where you get to try it: it is already behind the gateways you use. Vercel AI Gateway inside 48 hours, and at 2,341 likes that is the company's second-biggest post, behind only the stealth announcement.
https://x.com/typesafeai/status/2100376436272173088
Cloudflare AI Gateway, 749 likes, and OpenRouter in beta, 387 likes, the same week. Direct access is \POST [https://api.typesafe.ai/v1/systemone](https://api.typesafe.ai/v1/systemone)\ with a Bearer token.
⚖️ The honest caveat
The Hacker News launch thread, "Introducing System One Models and Jev", 1,863 points and 490 comments, spent most of its length on one phrase from the marketing:
Also 'can't hallucinate' seems wrong? Sure, it can't emit an invalid type, but it can still emit a completely wrong valid value.
- jacobgold, Hacker News launch thread, 1,863 points
Diogo did not fight it. When a commenter laid out that this is a classification model rather than an LLM, he called the explanation "very accurate!" and added only that he would say zero-shot rather than instruction-tuned. That is the honest framing, and it is a good deal smaller than what the launch-day hype was calling a new kind of intelligence: a very good zero-shot classifier with calibrated probabilities and a real API.
Reddit's biggest Jev thread is about who built it first. r/LocalLLaMA's "I literally built the Jev architecture one year back and completely open-sourced it with model, dataset and paper", 1,568 upvotes and 164 comments, drew the reply that sums up the whole industry's mood:
But did you post it saying it's the next big thing? Rookie mistake
- hapliniste, Reddit, 495 upvotes
The 351-upvote consolation in the same thread: because of that prior work, nobody gets to patent the general idea and lock it away.
Every's Mike Taylor put 12 passages with planted defects through Jev and through Fable 5.1 at high effort. Jev came back at a median 0.35 seconds per passage against 8.83, roughly 25 times faster and about 580 times cheaper. It also caught six of the seven defects. Fable caught all seven. His verdict: useful as an early warning system, because the alternative is not checking at all. A second, smaller side-by-side on a research loop against gpt-6-astra came out around 7x end to end, median decision 213ms against 2,436ms, both lanes 3 of 3 correct, which is real and useful and a long way from 200x. TypeSafe's own four-workflow average, as AISeeKing read it off their chart, is 67.8% agreement with the reference answers.
The hype fatigue is real too. The top comment, 262 likes, on a 75,750-view explainer that opened with "I genuinely believe it could be a game changer" was "Might be my least favorite sentence of all time."
And the sharpest reaction in the entire sweep was a viewer who watched a full explainer and came out the other side empty handed:
I watched this whole video and still have no idea what JEV is or does.
- Nullzero98, YouTube, 19 likes
That comment is why this article exists. The rule that resolves it comes from a developer who has been building this way for years anyway, and it fits on a sticker: AI executes, code decides.
🔍 How I picked these
Eleven /last30days runs across X, YouTube, Hacker News, Reddit, TikTok, Instagram, Digg, GitHub and arXiv returned 716 items. I read every raw file in full, then opened every post with real traction and checked its numbers against the live page, because the biggest posts about a two-day-old product were not where the keyword search expected them. 39 candidate workflows had a named source and a real number. I kept 9. No more than two picks lean on any one author or channel. Every engagement figure is what X or YouTube displayed at pull time, rounded exactly the way they round it.
On the code: four payloads are verbatim. The email triage block is TypeSafe's own quickstart from their docs, the raw JSON shape is from the same docs, and the two middleware blocks are copied from LangChain's post. Alex Volkov's compaction install line is his exact wording. I wrote the RAG filter myself against the documented API in the shape Kush described, and it is a draft with good bones rather than something anyone has run in production.
Embeds are reserved for posts that earned attention. Everything under a few hundred likes is linked inline instead, because a small post blown up into a quote card only looks like evidence.
🔑 Patterns across the picks
- Fast model reacts, slow model plans. Minecraft, the Wikipedia race in the launch thread, Browser Use and compaction all run the same split.
- Feed it candidates. The winners never ask Jev to generate an option. They build the option set in code, from the DOM, the retriever, the tool trace, the launcher index, and let it pick.
- Free output tokens are doing more work than the speed number. Every per-row and per-chunk workload here is unlocked by price.
- The confidence score is the product. Without a calibrated number to threshold on, this is a fast classifier. With one, it is a decision layer that knows when to stop.
- The interface is the invention, not the weights. Three working clones in 72 hours, and the biggest Reddit thread is someone who published the architecture a year ago.
- The academic version arrived first. TabAgent on arXiv makes the same argument for replacing routing, gating and verification calls with classifiers, without a product attached.
- The community already coined the right name for it. A builder cataloguing what people were shipping landed on "AI if statement", which is the most useful three words written about the model so far.
🧵 What I would do with it
Keep the big model for the hard thinking and the writing. Put this on every cheap judgment in the loop, threshold on confidence, and escalate anything under 0.5 to a bigger model or a human. Install the compaction plugin today, because that is the one you will feel by tonight.
📊 All Agents Reported Back
Reddit 113 threads / 24,425 upvotes / 4,159 comments; X 314 posts / 30,192 likes / 1,538 reposts, plus 13 posts verified by hand against the live page; YouTube 75 videos / 4,545,636 views; TikTok 36 videos / 171,040 views; Instagram 14 reels / 10,778 likes; Hacker News 133 stories / 25,312 points / 11,852 comments; GitHub 6 repos / 842 stars; Digg 7 clusters / 119 posts; arXiv 18 papers. Compiled from eleven /last30days runs on 2026-09-17, counts gross across runs before dedupe.
