Back to feed

Jev: The System 1 Model That 10x's Your Claude Code

TypeSafe's first System 1 model Jev comes from ChatGPT co-creator Diogo Almeida's team. With sub-second responses, 24x cheaper than Haiku and 230x cheaper than Fable 5.1, it brings speed and economy to Claude Code.

Imported to Nodesdaily: (UTC+03:00)
Watch on YouTube — tTnUcSj-QPA
Reading options

Device speech is unavailable in this browser.

Concept lens

Choose a technical term in this view to read its general definition, teaching example and use in the article.

No terms from our glossary were found in this view. The glossary does not cover every term yet.

In Jay E's RoboNuggets live demo, Jev answers in under a second. The opening claim is clear: built by a team including ChatGPT co-creator Diogo Almeida, this new model runs in a completely different lane from classic chat models. The announcement post reached 38 million views and the message is one line: make decisions in structured form, without generating free-form text.

Price and Speed: Why So Cheap and Fast?

The numbers are aggressive. TypeSafe's pricing shows Jev at about 24x cheaper than Haiku and 230x cheaper than Fable 5.1. Input costs $0.04 per million tokens, output is free. The headline claims are 20 to 200x speed and 40 to 400x lower cost; in the controlled workflow measurements on the TypeSafe blog the ceiling is given as 193.6x faster and 444.6x cheaper. So not your everyday average, but a lab ceiling under specific workflows.

The secret is constraint. Jev answers in only three shapes: binary true/false, pick from a list, and a 0-to-10 scale. It looks like a heavy limitation at first, but Jay E's point is that the narrow output stops the model from fabricating text; instead it returns a well-calibrated decision with probabilities. With all that generative variance removed, latency and cost collapse.

TypeSafe frames the split with Daniel Kahneman's Thinking, Fast and Slow. Jev is the first System 1 model; Fable and Astra-like large language models are System 2. System 2 gains flexibility by emitting token by token but gets slow. System 1 is fast, intuitive, schema-guaranteed and does not hallucinate. The best architecture is to pair them: Jev for fast classification, Claude for nuanced generation.

Access is now open. There was a waitlist during recording, but TypeSafe opened early access to everyone by the time the video went live. You can get a key directly from TypeSafe or connect in one command via OpenRouter. Jay E used OpenRouter in his own setup and showed a single-command setup instruction on screen; a free PDF with all commands sits in the description.

Level 1: Speeding Up the Agent OS

Level one is making your existing agent setup faster and cheaper. First trick is model routing. Using the most expensive model for everything makes no sense; Opus and Fable are pricey while Haiku and Sonnet handle many tasks fine. The problem was that picking the right model fell to you. Jev automates that choice. In Jay E's 12-prompt comparison, Jev-guided routing saved 70% because 9 tasks did not need the strongest model at all.

In practice he suggests a skill command to toggle it: type /Jev on and every task in that session gets routed by Jev to the best-fit model. In the example, finding the file path of the Jev prompt was routed to Haiku; without Jev the session default would have been Opus 5. Token economy is protected by a one-line router.

Second trick is skill discovery. Jay E's workspace holds 145 skills. In a 14-test benchmark, Jev found the correct skill in about 5 seconds, while the default Opus 5 approach took 30 seconds. Logic is simple: input is your task, options are your skill list, Jev pulls the right skill instantly for Claude to load. A one-command instruction can be copied to try it yourself.

Levels 2 and 3: From Business Automation to New Apps

Level two is business automation. The demo classifies 800 emails with a single business question: which ones are real prospects to contact? Jev, Haiku and Fable run side by side; on play, Jev tags the whole list as interested / not a prospect / not interested in under a second. The others are visibly slower and more expensive. The pattern is clear: high-volume data plus a single business question is a perfect fit for Jev.

Jay E generalizes the pattern. Invoice fraud detection is a huge industry; spam filters, community management, high-volume refund requests and churn prediction for subscription businesses fit the same template. The question to ask in your company is: what do you receive in bulk that needs classifying? Put Jev there and automation drops to a few text commands.

Level three is apps now possible because the cost barrier fell. In Jay E's Rubrik system holding hundreds of images and videos, filename search finds only files with that word in the name while Jev-powered semantic search returns by meaning and typing Claude surfaces genuinely Claude-themed visuals. In the same logic Kitsi's Chrome extension Unclutter classifies every page element in the background with Jev and cleans ads and cookie banners in one click.

Visualization: nodesdaily AI

AI commentary

"I think Jev's brilliance hides in its constraint. By settling for only three output shapes and refusing open text generation, it eliminates hallucination and slashes cost. For me the real lesson is to run Jev not alone but hybrid with a System 2 like Claude."

AI assessment

Steel-manned, the opposing view says Jev's narrow schema is a weakness. Any task that does not fit the three shapes leaves the model mute; where long text generation, open-ended reasoning or a creative leap is expected, Jev alone falls short. The critique is fair but incomplete: TypeSafe does not sell Jev as a chat model but as a decision layer. Judging it like a novel-writing calculator misses the point.

Limits are more nuanced in practice. Jev does not hallucinate and guarantees schema, yet calibration quality still depends on domain data and careful domain engineering. The 193x speed and 444x cost figures on the blog are averages over four real workflows and the authors themselves flag them as a ceiling, not an everyday average. Early access is now open, but training data is TypeSafe's own synthesis and public benchmarks are deliberately not published. Generalizing without a small validation set on your own data would be optimistic.

On incentives and transparency, two notes stand out. TypeSafe says it will not train on your data and roots that claim in a data-lab identity; that is reassuring for enterprise use. At the same time the video is both a tutorial and a pitch for the RoboNuggets community. Jay E frames routing and automation examples within his product and membership context. That does not invalidate the content, but it puts the burden on the viewer to verify price and speed on their own data.

Where to use it in practice? Jev shines where volume is high and the question is crisp: triaging an inbox, picking a skill, filtering invoices or spam. Where edge cases, nuance and long-context reasoning dominate, keep a System 2 like Claude in front. The lowest-risk start, as Jay E suggests, is to try routing and skill discovery, measure savings and accuracy in logs, then expand to bulk classification jobs.

Sources

6 links; 1 of them also cited by 3 other stories. Stories sharing a link do not confirm each other; a source's origin is not inferred from how often it is cited.

jev · typesafe · claude code · system 1 · artificial intelligence

Follow the topic

Before this story

A short reading order from earlier stories linked to this event by an editor.

Evidence and sources

Review permitted source passages, versions and origins.

KAYNAKLARLA OKU

Bu haberi açalım.

Hesap kontrol ediliyor…