
Updated Nov 13, 2026
What people are building with Jev
855 projects, posts and guides about Jev, the System One model from TypeSafe AI. Each entry links to its source and shows the cost and speed its author reported.
- 855builds
- 182guides
- 21use cases

Diogo Almeida
@CompleteSkeptic
After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x cheaper (w/ output tokens free) • Frontier composable intelligence optimized for decisions AFAICT the shortest path to AI-based economic revolution


GitHubTools and apps
ST-jeved
A SillyTavern extension that measures each reply before it lands.
mossyfield
33

Erick
@ErickSky
Este tipo de herramientas empieza a hacer que el contexto de los agentes parezca menos una ventana limitada y más una memoria que se administra dinámicamente. [fast-jev-compaction] No resume, hace que Jev analice cada tool call y su resultado para decidir qué sigue siendo necesario. - Lo que importa se queda verbatim. - Lo que ya no aporta, se elimina. - Y los resultados que todavía pueden ser útiles permanecen intactos. Además: • Funciona como plugin de Claude Code • También puedes usarlo como librería npm • Las decisiones se toman sobre el contexto completo • Puede truncar resultados o eliminarlos junto con su llamada • Mantiene intactos los mensajes de usuario y assistant • Tiene fallback al compaction tradicional de Claude Code En otras palabras: En vez de resumir tu memoria, intenta podarla. REPOOO👇
Guidex.com
The compaction plugin, in Spanish
Erick on fast-jev-compaction: instead of summarising the context, Jev prunes it, keeping what matters word for word.

GitHubOpen source
open-spark-jev
Local System One models on Qwen3, for an NVIDIA DGX Spark.
Abhishek Rai
23
GitHubBenchmarks and evals
ChatJev
Driving the classifier as a next-token predictor, one token at a time.
Erik Dunteman
7
GitHubCoding and code review
jev-auto-approve
A pull request approver that asks Jev before it approves.
MetalBear
9
Theo - t3.gg
@theo
This is a terrible compaction strategy that fundamentally doesn't understand how compaction and context management work. Seems like a lot of people are confused so let's break this down. 1. Compaction isn't a filter The role of compaction is to clean up history to keep the agent focused, not just deleting noise. It should be used sparingly when context gets too long, not constantly to keep context small. 2. Jev doesn't even know what it's deciding on! Models use the context of the thread to decide what to keep or not keep in a summary. This implementation goes through on a "line-by-line" (per tool call) basis to decide what should be left or deleted. Not only does this 32k token context model know very little of what happened before, but (in this implementation) it doesn't even know what the result of the tool call is! Deleting these things randomly will keep the model from knowing what it's tried and dooms you to end up in "stupid loops" where the model keeps trying the same thing over and over. 3. You're giving up the reasoning entirely Frontier models from OpenAI, Anthropic, XAI, and Google do not share reasoning traces over the API. They share encrypted payloads, which Jev cannot see (and often will drop). Anthropic is even stricter with this, requiring you to preserve the entire history in order to get any of the reasoning data. As a result, using this in Claude Code guarantees the model will act way dumber. 4. Models are tuned on their compaction flows For the last year, Frontier Labs have been including compaction and long runs as part of the training process. These models have learned ways to compact that are more effective than any rudimentary solution. Fun fact: If you switch models in Codex and compaction is necessary, compaction will run on the model that was previously used in the thread. 5. Cache writes are more expensive than cache reads. Cache writes are the biggest cost by far for agents. I often see cache write costs go over 60% of my total LLM spend in my personal use of Claude Code and Codex. Cache writes are insanely expensive when data earlier in the history is changed (because the old cache is invalidated when things change at the top). Every history edit requires a cache rewrite for ANY data past the history edit. If your history is "1,2,3,4,5,6" and you delete "2", you have to rewrite "3,4,5,6". This is more expensive than leaving "2" in the history. Good news. Since we're already killing all of the reasoning tokens by doing this stupid compaction strategy, the rewrite cost won't actually be that high because the model is missing so much data! 🙃🙃 6. The implementation is hot garbage. > "Whatever is not kept is deleted permanently, but the assistant can always re-run a tool or re-read a file." Good luck with that one. To be clear: this is a cool experiment and I find it genuinely interesting. That said, if you think this style of bs filtering on a probability threshold is actually a compaction strategy, I highly recommend you just use the defaults in tools like Claude Code and Codex. You're much less likely to hurt yourself that way.
Guidex.com
The case against Jev compaction
Theo on why per-tool-call filtering is not compaction: lost reasoning, higher cache-write costs and agents stuck in loops.

GitHubAgents and browsers
pi-jev-skill-picker
Ranks the Pi agent’s skills for the task in front of it.
Safzan Pirani
36
GitHubRouting and model choice
pi-jev-router (win4r)
Model routing at task boundaries, with caching and failover.
Chao Qin
11
Guideyoutube.com/@GregIsenberg
Jev is HERE. How to use it
Greg Isenberg and Ryan Vogel on the Startup Ideas Pod: what Jev is, the businesses it unlocks, and how to call it today through the Vercel AI Gateway.


GitHubBenchmarks and evals
jev-architect
Helps you find, design and evaluate a Jev decision loop.
Karan Bansal
7
Guideyoutube.com/@syntaxfm
wtf is jev?
CJ from Syntax explains how Jev works, then demos browser use, classification, code review, a model router and a chat bot with no LLM.

GitHubContext and memory
jev-harness
Every tool result is filtered by Jev before the model reads it.
AstroHan
6
GitHubCoding and code review
jev-spec
Checks generated code against the specification that asked for it.
Nozomi Koborinai
11
GitHubRouting and model choice
jev-tool-router
Picks the MCP tool for Codex, instead of listing them all.
jackbarunz
9Guideyoutube.com/@vogeldev
Meet Jev: tested on 1,000 emails
Ryan Vogel runs Jev on 100 and then 1,000 of his emails: category, priority, spam and reply predictions.



GitHubBenchmarks and evals
jev-design
A console whose design system is chosen by Jev at runtime.
Gonzalo Bilune
57Guideyoutube.com/@AICodeKing
Jev and Browser Use, fully tested
AICodeKing tests support routing, refund detection, prompt-injection resistance and browser automation.



GitHubContext and memory
perfectrecall
Agent memory where Jev decides what is worth recalling.
Arslan R.
3Guideyoutube.com/@retriever-ai
Jev in the rtrvr.ai browser agent
Retriever AI tests Jev on real browser tasks: where it worked, where it struggled, and how they will use it next to larger models.

GitHubBenchmarks and evals
JevGuard
A decision runtime with zero-token caching and a calibrator.
Seb4Ez
0
GitHubAgents and browsers
jev-cua
A local computer-use fast path for Codex and Waku.
Eronmonsele Aigbiluese
0
GitHubRobotics and devices
home-assistant-typesafe
Home Assistant routes what you said through Jev, not an LLM.
Allen Porter
2Guideyoutube.com/@NidhiSinghAttri
Jev and herdr: routing between models
Nidhi Singh’s setup: one terminal, three AI subscriptions, and Jev picks the model for Claude Code, Codex and Cursor.


GitHubCoding and code review
The Jev-enator
Three Claude Code hooks that each ask Jev a question.
Jake Reardon
0