Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is pure f*cking gold for anyone doing Jev engineering the skill that teaches Claude Code to build on Jev the right way, from TypeSafe themselves without it, coding agents send Jev one question at a time and guess the field names with it, the order is set before...

polydao's profile picture

Mr. Buzzoni

25,516 subscribers

28,212 görüntüleme • 5 gün önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

12 Yorum

💁🏽‍♂️Aston🦦 profil fotoğrafı
💁🏽‍♂️Aston🦦4 gün önce

yall AI accounts all do these cringe ass reposts in the same style its so fucking inauthentic holy shit! Woah! Fucking gold! Tiresomemuch

Elvar profil fotoğrafı
Elvar5 gün önce

the math is too good

catman profil fotoğrafı
catman5 gün önce

Defining behavior and batching judgments first lets one request resolve multiple semantic decisions, so the agent spends fewer calls guessing fields one at a time.

Phanindra Malladi profil fotoğrafı
Phanindra Malladi5 gün önce

typed skills beat dumping docs into context. that is how claude code stops guessing field names.

Stanislav Sorokin profil fotoğrafı
Stanislav Sorokin4 gün önce

We point Jev at Claude Code the other way: it reads each sub-task and picks the builder in 0.44 s, about 0.004 cents a pick. The surprise was which tasks it keeps away from Sonnet. Does this skill route models too?

Troy profil fotoğrafı
Troy4 gün önce

Got my local fine tuned Jev style decision model playing Diablo II in real time! Possibilities are endless now.

leopardracer profil fotoğrafı
leopardracer5 gün önce

batching only helps if the 13 questions don't depend on each other. if #6 needs #3's answer first, it's one call at a time again

karcharodon profil fotoğrafı
karcharodon5 gün önce

This is really an gold

Iron Mind profil fotoğrafı
Iron Mind4 gün önce

JEV engineering is a new chapter for devs

Eugene Oldman profil fotoğrafı
Eugene Oldman5 gün önce

batching showed up in most jev builds

0xSlyth profil fotoğrafı
0xSlyth5 gün önce

Jev cuts cost by batching decisions smartly

COSMOS profil fotoğrafı
COSMOS4 gün önce

jev

Benzer Videolar

this is pure f*cking gold for anyone running coding agents Jev founder, Diogo Almeida, wrote a guide on building a Jev harness the expensive model only writes the code. every fork around it goes to Jev the bill: > 6,000 forks a day on a frontier model: $180 > the same 6,000 forks on Jev: $0.25 > the whole harness, patches included: about $24 99 percent of what's left is the code itself, which is the only part you should be paying for what's inside: > the turn snapshot, five hooks, the cascade > thresholds read off your own receipts > the one rule a model never gets a vote on one evening of setup and your agent stops paying frontier prices to answer yes or no ↓
0:30

this is pure f*cking gold for anyone running coding agents Jev founder, Diogo Almeida, wrote a guide on building a Jev harness the expensive model only writes the code. every fork around it goes to Jev the bill: > 6,000 forks a day on a frontier model: $180 > the same 6,000 forks on Jev: $0.25 > the whole harness, patches included: about $24 99 percent of what's left is the code itself, which is the only part you should be paying for what's inside: > the turn snapshot, five hooks, the cascade > thresholds read off your own receipts > the one rule a model never gets a vote on one evening of setup and your agent stops paying frontier prices to answer yes or no ↓

Hanako

20,837 görüntüleme • 6 gün önce

this is pure f*cking treasure 10 GitHub projects that put Jev between your agent and every decision your agent should stop paying a frontier model to answer yes or no ROUTE THE WORK 01 jev-router > 02 jcm-router > 03 jev-agent-skill-router > GUARD EVERY ACTION 04 pi-heed > 05 fx > 06 Foreman > SCORE WHAT MATTERS 07 LlamaIndex Jev > 08 citation-verifier > PUT IT TO WORK 09 yoshi > 10 mastra-jev-moderation > the loop: your agent hits a fork > Jev answers with a probability > your code decides what that number allows > the agent moves on 3 builds I'd explore: coding agent: jev-router > fx > Foreman > yoshi support desk: jev-agent-skill-router > mastra-jev-moderation > LlamaIndex Jev research: jcm-router > pi-heed > citation-verifier save this, then build a decision layer for your agents ⭣
0:32

this is pure f*cking treasure 10 GitHub projects that put Jev between your agent and every decision your agent should stop paying a frontier model to answer yes or no ROUTE THE WORK 01 jev-router > 02 jcm-router > 03 jev-agent-skill-router > GUARD EVERY ACTION 04 pi-heed > 05 fx > 06 Foreman > SCORE WHAT MATTERS 07 LlamaIndex Jev > 08 citation-verifier > PUT IT TO WORK 09 yoshi > 10 mastra-jev-moderation > the loop: your agent hits a fork > Jev answers with a probability > your code decides what that number allows > the agent moves on 3 builds I'd explore: coding agent: jev-router > fx > Foreman > yoshi support desk: jev-agent-skill-router > mastra-jev-moderation > LlamaIndex Jev research: jcm-router > pi-heed > citation-verifier save this, then build a decision layer for your agents ⭣

delost

15,734 görüntüleme • 6 gün önce

this is f*cking gold 20 GitHub repos with 500K+ combined stars that will level up your JEV workflow AGENTS > jev-ultrafast: Jev picks every click and DOM target, a small LLM only types > hermes-jev-skills: routing, memory, compaction and skill picks in one pack > typesafe-computer-use: OCR reads your Mac screen, Jev picks the next click MEMORY > fast-jev-compaction: scores every tool call keep, truncate or drop instead of summarizing > jevmem: project memory for Claude Code, Cursor and Codex, updated every turn > jev-second-brain: your Obsidian vault, Jev judges which notes duplicate, revise or contradict SAFETY > jev-guard: a gate before every tool call, Jev scores the risk, you set allow, ask or deny TOOLS > skills: the official TypeSafe skill for Claude Code and Codex > system-one-adapter-python: dry-run your questions on an ordinary LLM before you burn a Jev key > jev-mcp: claim checks, screening and ranking as MCP tools > typesafe-mcp: plug Jev into any MCP client > json-render: Vercel's generative UI, where Jev picks the components OPEN MODELS > SemIf-OpenJev: semantic ifs from frozen open models kev: Jev-like models on Qwen that run on your MacBook > laya-mlx: the Laya decision engine on Apple silicon > clm: an open System One model with Choice, Noul and Score > jevlike: train your own Jev-like model TRADING > jev-trader: one buy or sell decision per Monad block START HERE > awesome-jev: the biggest map of everything built on Jev > awesome-jev-by-typesafe: use cases, patterns and starter code bookmark it before your next build
0:22

this is f*cking gold 20 GitHub repos with 500K+ combined stars that will level up your JEV workflow AGENTS > jev-ultrafast: Jev picks every click and DOM target, a small LLM only types > hermes-jev-skills: routing, memory, compaction and skill picks in one pack > typesafe-computer-use: OCR reads your Mac screen, Jev picks the next click MEMORY > fast-jev-compaction: scores every tool call keep, truncate or drop instead of summarizing > jevmem: project memory for Claude Code, Cursor and Codex, updated every turn > jev-second-brain: your Obsidian vault, Jev judges which notes duplicate, revise or contradict SAFETY > jev-guard: a gate before every tool call, Jev scores the risk, you set allow, ask or deny TOOLS > skills: the official TypeSafe skill for Claude Code and Codex > system-one-adapter-python: dry-run your questions on an ordinary LLM before you burn a Jev key > jev-mcp: claim checks, screening and ranking as MCP tools > typesafe-mcp: plug Jev into any MCP client > json-render: Vercel's generative UI, where Jev picks the components OPEN MODELS > SemIf-OpenJev: semantic ifs from frozen open models kev: Jev-like models on Qwen that run on your MacBook > laya-mlx: the Laya decision engine on Apple silicon > clm: an open System One model with Choice, Noul and Score > jevlike: train your own Jev-like model TRADING > jev-trader: one buy or sell decision per Monad block START HERE > awesome-jev: the biggest map of everything built on Jev > awesome-jev-by-typesafe: use cases, patterns and starter code bookmark it before your next build

NO1ennn

18,445 görüntüleme • 5 gün önce

this harness stack is f*cking gold TypeSafe AI + LangChain finally dropped the layer that makes agents affordable at company scale: jev running inside the langchain agent loop as middleware the problem every big team hits: each fork in the loop is another full LLM call. at 10 agents that's a bill. at 10,000 it's the budget > routing before: every task goes to the frontier model now: jev picks the least costly model that can finish it. lookups go fast, architecture goes powerful > guardrails before: the "is this command dangerous?" check sat in the closed parts of claude code, codex, cursor now: AutoModeMiddleware(tools=["bash"]). one line, any agent, blocked before the tool runs > decisions before: one LLM call per question now: every question about the same state in one request, answered in parallel > audit before: "the model decided" now: the answer, the probability and the confidence stay in agent state > adoption no rewrite. pip install langchain-typesafe and drop it into the agent you already run TypeSafe reports up to 200x faster inference and 400x lower cost than comparable LLMs on classification. the LLM still reasons and writes. jev takes the thousands of small calls in between already live: browserbase agents for fractions of a cent, a live trading agent, email triage at scale full loop mapped below: 7 agents, 4 jev gates per step count the forks in your agent loop tonigh
0:22

this harness stack is f*cking gold TypeSafe AI + LangChain finally dropped the layer that makes agents affordable at company scale: jev running inside the langchain agent loop as middleware the problem every big team hits: each fork in the loop is another full LLM call. at 10 agents that's a bill. at 10,000 it's the budget > routing before: every task goes to the frontier model now: jev picks the least costly model that can finish it. lookups go fast, architecture goes powerful > guardrails before: the "is this command dangerous?" check sat in the closed parts of claude code, codex, cursor now: AutoModeMiddleware(tools=["bash"]). one line, any agent, blocked before the tool runs > decisions before: one LLM call per question now: every question about the same state in one request, answered in parallel > audit before: "the model decided" now: the answer, the probability and the confidence stay in agent state > adoption no rewrite. pip install langchain-typesafe and drop it into the agent you already run TypeSafe reports up to 200x faster inference and 400x lower cost than comparable LLMs on classification. the LLM still reasons and writes. jev takes the thousands of small calls in between already live: browserbase agents for fractions of a cent, a live trading agent, email triage at scale full loop mapped below: 7 agents, 4 jev gates per step count the forks in your agent loop tonigh

NO1ennn

31,666 görüntüleme • 5 gün önce

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... *ahem*... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.
1:02

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... *ahem*... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Ben Dicken

40,810 görüntüleme • 14 gün önce

ANTHROPIC LEAKED A $4.2M FILE WHERE 4 AGENTS BUILD THE JEV SYSTEM IN 60 MINUTES, DOING $100K A MONTH four agents cost $0, and the system they assemble in an hour generates $100K a month scout → builder → critic → operator → JEV every agent is pinned to one exact model version, and none of them runs on "latest" the scout on Haiku 4.5 reads the market, the builder on Sonnet 5 builds everything, the critic on Opus 5 decides what ships the operator runs Haiku through the batch API at half price - the one agent that never has to hurry the builder takes 59% of the whole hour, because it's the one writing, and writing costs 5x more than reading short answers are cheap answers - and the whole economics rests on that one rule pin the versions in ROOT.md and next month JEV behaves exactly the same point it at "latest" and the model underneath updates quietly, no error, and the answers start to drift $100K a month is 334 customers at $299 four versions, one system - pin them and JEV stays JEV save this and paste it into Claude Code - let it build you these 4 agents ↓
1:28

ANTHROPIC LEAKED A $4.2M FILE WHERE 4 AGENTS BUILD THE JEV SYSTEM IN 60 MINUTES, DOING $100K A MONTH four agents cost $0, and the system they assemble in an hour generates $100K a month scout → builder → critic → operator → JEV every agent is pinned to one exact model version, and none of them runs on "latest" the scout on Haiku 4.5 reads the market, the builder on Sonnet 5 builds everything, the critic on Opus 5 decides what ships the operator runs Haiku through the batch API at half price - the one agent that never has to hurry the builder takes 59% of the whole hour, because it's the one writing, and writing costs 5x more than reading short answers are cheap answers - and the whole economics rests on that one rule pin the versions in ROOT.md and next month JEV behaves exactly the same point it at "latest" and the model underneath updates quietly, no error, and the answers start to drift $100K a month is 334 customers at $299 four versions, one system - pin them and JEV stays JEV save this and paste it into Claude Code - let it build you these 4 agents ↓

Sprytix

37,977 görüntüleme • 13 gün önce

Jev founder, Diogo Almeida, just put out a PDF on building a Jev harness for coding agents the claim: 200x faster, 400x cheaper the model stopped being the bottleneck a while ago. the harness around it is where the cost and the speed actually live five decisions sit on every loop, and only one of them writes code hand this PDF and the article below to your Claude Code or Codex instance and let it rebuild its own setup your agent gets a better harness tonight, and monday looks different than it would have 👇
0:23

Jev founder, Diogo Almeida, just put out a PDF on building a Jev harness for coding agents the claim: 200x faster, 400x cheaper the model stopped being the bottleneck a while ago. the harness around it is where the cost and the speed actually live five decisions sit on every loop, and only one of them writes code hand this PDF and the article below to your Claude Code or Codex instance and let it rebuild its own setup your agent gets a better harness tonight, and monday looks different than it would have 👇

Hanako

37,887 görüntüleme • 9 gün önce

Jev has been exploding in popularity recently. If you already have access to the Jev API but aren't sure how to start experimenting with it, just copy this checklist: 1. jev-ultrafast Browser Use's fastest agent. Jev decides the next action and which element to click, and a language model is only called when text has to be typed. 2. typesafe-mario Jev plays Super Mario Bros. from structured emulator state, choosing every action from features pulled out of the game. 3. jev-plays-pokemon Reads Pokémon Red's game state as text, answers typed questions each turn, and lets plain code turn the answers into moves. 4. jev-drone A camera-only autonomous drone in MuJoCo with a Jev judgment model sitting in the control loop at 2.5 Hz. 5. robo-harness A real SO-101 robot arm workbench where Jev picks bounded joint steps from typed candidate actions under a spend budget. 6. fast-jev-compaction Claude Code plugin that replaces the compaction summary with Jev decisions, scoring every tool call for whether it is still needed. 7. jev-claude Routes Claude Code's own judgment calls through Jev: typed choices with probabilities at plan approval, on questions, and before risky commands. 8. is-malicious Supply-chain check before you run anything: Jev Noul checks over source and build files, returning the implicated files and lines. 9. sqlite-jev Jev inside SQL. Noul, Choice and Score judgments exposed as SQLite functions, with confidence on every row. 10. jevinci Paints images by having Jev predict every pixel's colour in parallel, with confidence deciding how wide each stroke is drawn. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓
0:32

Jev has been exploding in popularity recently. If you already have access to the Jev API but aren't sure how to start experimenting with it, just copy this checklist: 1. jev-ultrafast Browser Use's fastest agent. Jev decides the next action and which element to click, and a language model is only called when text has to be typed. 2. typesafe-mario Jev plays Super Mario Bros. from structured emulator state, choosing every action from features pulled out of the game. 3. jev-plays-pokemon Reads Pokémon Red's game state as text, answers typed questions each turn, and lets plain code turn the answers into moves. 4. jev-drone A camera-only autonomous drone in MuJoCo with a Jev judgment model sitting in the control loop at 2.5 Hz. 5. robo-harness A real SO-101 robot arm workbench where Jev picks bounded joint steps from typed candidate actions under a spend budget. 6. fast-jev-compaction Claude Code plugin that replaces the compaction summary with Jev decisions, scoring every tool call for whether it is still needed. 7. jev-claude Routes Claude Code's own judgment calls through Jev: typed choices with probabilities at plan approval, on questions, and before risky commands. 8. is-malicious Supply-chain check before you run anything: Jev Noul checks over source and build files, returning the implicated files and lines. 9. sqlite-jev Jev inside SQL. Noul, Choice and Score judgments exposed as SQLite functions, with confidence on every row. 10. jevinci Paints images by having Jev predict every pixel's colour in parallel, with confidence deciding how wide each stroke is drawn. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

Hanako

29,629 görüntüleme • 9 gün önce

LLMs vs. Jev, clearly explained! LLMs are great, and the ceiling is one you can watch scroll past: an LLM writes the answer one token at a time. give it a failed deploy and four decisions, and it produces a small JSON object where every token depends on the one before it. token nine cannot exist until token eight does, so four decisions that had nothing to do with each other just stood in a queue. then your code parses it, validates the shape, and retries when the shape is wrong. Jev fixes this without being a smaller or faster model: it removes the order. one turn on that deploy has to know: → whether the incident is urgent → which team owns it → whether the next command is risky → whether the task is actually done you declare the questions and the answer type upfront, and all four come back together, typed, with a probability on each. three primitives cover almost every fork in an agent: 1. **Choice** picks one of up to 255 options you define, like engineering, billing or sales. 2. **Score** places the state on an ordered scale you define, like low, medium or high risk. 3. **Noul** returns the probability that a yes-or-no condition is true. here is the sentence that resolves the whole confusion: text is a line you have to walk. an answer space is a room you see all of at once. ↳ generation: one order you cannot change, one string at the end, a shape you hope holds ↳ evaluation: no order at all, typed answers, a probability on every option Prompts → Agents → Loops → Graphs → Jev the probabilities matter more than the answer. ↳ engineering at 0.91 against billing at 0.09 is a route you can automate ↳ 0.52 against 0.46 is a coin flip wearing a label, and the label alone never told you which one you got that last one catches careful people. an LLM would have said "engineering" in a confident sentence and given you no way to know the race was that close. thresholds live in your code, one per action, scaled to what being wrong costs. it works when the options are known and the call depends on meaning. it is not for writing, code, arithmetic, or anything where question two needs the answer to question one. and the one that eats whole nights: type safety prevents malformed output, not incorrect judgment. Jev cannot return an option outside your schema, and it can still pick the wrong valid one with confidence. a schema-valid mistake refunds the wrong customer just as fast. an LLM writes new language when the answer space is open. Jev evaluates known paths when the answer space is closed. below i have quoted my full breakdown on Jev. it covers the three primitives, the parallel battery, the thresholds, and where it does not belong. save this and read it below ↓
0:35

LLMs vs. Jev, clearly explained! LLMs are great, and the ceiling is one you can watch scroll past: an LLM writes the answer one token at a time. give it a failed deploy and four decisions, and it produces a small JSON object where every token depends on the one before it. token nine cannot exist until token eight does, so four decisions that had nothing to do with each other just stood in a queue. then your code parses it, validates the shape, and retries when the shape is wrong. Jev fixes this without being a smaller or faster model: it removes the order. one turn on that deploy has to know: → whether the incident is urgent → which team owns it → whether the next command is risky → whether the task is actually done you declare the questions and the answer type upfront, and all four come back together, typed, with a probability on each. three primitives cover almost every fork in an agent: 1. **Choice** picks one of up to 255 options you define, like engineering, billing or sales. 2. **Score** places the state on an ordered scale you define, like low, medium or high risk. 3. **Noul** returns the probability that a yes-or-no condition is true. here is the sentence that resolves the whole confusion: text is a line you have to walk. an answer space is a room you see all of at once. ↳ generation: one order you cannot change, one string at the end, a shape you hope holds ↳ evaluation: no order at all, typed answers, a probability on every option Prompts → Agents → Loops → Graphs → Jev the probabilities matter more than the answer. ↳ engineering at 0.91 against billing at 0.09 is a route you can automate ↳ 0.52 against 0.46 is a coin flip wearing a label, and the label alone never told you which one you got that last one catches careful people. an LLM would have said "engineering" in a confident sentence and given you no way to know the race was that close. thresholds live in your code, one per action, scaled to what being wrong costs. it works when the options are known and the call depends on meaning. it is not for writing, code, arithmetic, or anything where question two needs the answer to question one. and the one that eats whole nights: type safety prevents malformed output, not incorrect judgment. Jev cannot return an option outside your schema, and it can still pick the wrong valid one with confidence. a schema-valid mistake refunds the wrong customer just as fast. an LLM writes new language when the answer space is open. Jev evaluates known paths when the answer space is closed. below i have quoted my full breakdown on Jev. it covers the three primitives, the parallel battery, the thresholds, and where it does not belong. save this and read it below ↓

Hanako

42,632 görüntüleme • 13 gün önce

Holy crap, who the hell did this?!! Someone open-sourced a Jev-powered second brain for AI agents and lets you plug it straight into your own agent. GitHub's already at 925 stars, repo's called Hermes-Jev-Skills. You just run one install command, and Jev takes over every tiny decision your agent burns premium tokens on. Which model answers, which skill to load, which memories matter, what survives when context gets cut. Give it your computer or browser and it'll pick the next click, but only from actions you already marked safe. It'll sort your inbox into lanes, strip hidden prompt injections out of search results, and triage every message in ~0.4 seconds. Claude Code and Codex support - they threw that in too. No dependencies, no patching Hermes core, and your API key never touches the agent Link's right here: The catch? Jev itself is a paid cloud API. The skills run on your machine; the decisions don't. But hey, a decision costs a fraction of a cent, everything fails open if Jev goes down, and your expensive model finally gets to do only the thinking. Who needs a damn frontier model picking which file to open!
0:31

Holy crap, who the hell did this?!! Someone open-sourced a Jev-powered second brain for AI agents and lets you plug it straight into your own agent. GitHub's already at 925 stars, repo's called Hermes-Jev-Skills. You just run one install command, and Jev takes over every tiny decision your agent burns premium tokens on. Which model answers, which skill to load, which memories matter, what survives when context gets cut. Give it your computer or browser and it'll pick the next click, but only from actions you already marked safe. It'll sort your inbox into lanes, strip hidden prompt injections out of search results, and triage every message in ~0.4 seconds. Claude Code and Codex support - they threw that in too. No dependencies, no patching Hermes core, and your API key never touches the agent Link's right here: The catch? Jev itself is a paid cloud API. The skills run on your machine; the decisions don't. But hey, a decision costs a fraction of a cent, everything fails open if Jev goes down, and your expensive model finally gets to do only the thinking. Who needs a damn frontier model picking which file to open!

Archive

16,841 görüntüleme • 3 gün önce

Everyone is talking about JEV. Almost nobody knows how to actually use it. These 10 GitHub repos fix that. 1. browser-use/jev-ultrafast (~16.6k⭐) Jev for browser agents: pick the next action without another expensive LLM call. 2. tamaratran/fast-jev-compaction (~6.5k⭐) Uses Jev to decide what context still matters and what can be dropped. 3. TheoLeeCJ/SemIf (~4k⭐) Open-source Jev-style decision making you can run locally. 4. jarrodwatts/jev-trader (~2.1k⭐) Real-time trading loop where Jev decides buy, sell or wait. 5. kerpopule/hermes-jev-skills (~670⭐) Jev routing, memory, compaction and skill selection for AI agents. 6. devagrawal09/jev-review (~570⭐) Code review powered by Jev decisions instead of one giant prompt. 7. thruwire/foreman (~520⭐) Jev as a supervisor for coding agents: continue, retry, verify or stop. 8. superagents-lab/jev-search (~400⭐) Jev decides where and how an agent should search. 9. droidrun/mobile-jev (~350⭐) Jev for Android agents choosing the next app action. 10. gargpratyush/jev-router (~340⭐) Routes agent tasks to the right model with Jev. After looking through these, the pattern is pretty clear: LLMs generate. Agents execute. JEV decides. That decision layer is what most agent stacks are still missing. Save this if you want to integrate Jev into your workflow👇
1:11

Everyone is talking about JEV. Almost nobody knows how to actually use it. These 10 GitHub repos fix that. 1. browser-use/jev-ultrafast (~16.6k⭐) Jev for browser agents: pick the next action without another expensive LLM call. 2. tamaratran/fast-jev-compaction (~6.5k⭐) Uses Jev to decide what context still matters and what can be dropped. 3. TheoLeeCJ/SemIf (~4k⭐) Open-source Jev-style decision making you can run locally. 4. jarrodwatts/jev-trader (~2.1k⭐) Real-time trading loop where Jev decides buy, sell or wait. 5. kerpopule/hermes-jev-skills (~670⭐) Jev routing, memory, compaction and skill selection for AI agents. 6. devagrawal09/jev-review (~570⭐) Code review powered by Jev decisions instead of one giant prompt. 7. thruwire/foreman (~520⭐) Jev as a supervisor for coding agents: continue, retry, verify or stop. 8. superagents-lab/jev-search (~400⭐) Jev decides where and how an agent should search. 9. droidrun/mobile-jev (~350⭐) Jev for Android agents choosing the next app action. 10. gargpratyush/jev-router (~340⭐) Routes agent tasks to the right model with Jev. After looking through these, the pattern is pretty clear: LLMs generate. Agents execute. JEV decides. That decision layer is what most agent stacks are still missing. Save this if you want to integrate Jev into your workflow👇

unicode

20,745 görüntüleme • 10 gün önce

Jev Engineering turns a static agent workflow into a graph that can rewrite itself while running. the video is basically the problem at scale: hundreds of routes → thousands of crossings → different agents → different tools → different confidence levels Jev Engineering doesn’t control every step. it controls the crossings. when two paths compete: → score both → kill the weak route → reroute the task so instead of one fixed chain, you get a live braid: state → decision → parallel paths → crossings → Jev → next state that’s the point of Jev Engineering: more parallel execution without letting the system lose the objective. the agents create the paths. Jev decides which paths survive. full breakdown below ↓
0:41

Jev Engineering turns a static agent workflow into a graph that can rewrite itself while running. the video is basically the problem at scale: hundreds of routes → thousands of crossings → different agents → different tools → different confidence levels Jev Engineering doesn’t control every step. it controls the crossings. when two paths compete: → score both → kill the weak route → reroute the task so instead of one fixed chain, you get a live braid: state → decision → parallel paths → crossings → Jev → next state that’s the point of Jev Engineering: more parallel execution without letting the system lose the objective. the agents create the paths. Jev decides which paths survive. full breakdown below ↓

Ricker

11,145 görüntüleme • 9 gün önce

this is f*cking gold 12 open-source repos that plug Jev into real AI work, 550.7k stars combined Jev decides, your LLM writes. these repos are where that split already runs: agents > browser-use/jev-ultrafast (~20.3k): Jev picks the next action + DOM element, a small LLM only types. Zürich to London flights in ~7s > awlevin/typesafe-computer-use (~978): macOS computer use, OCR reads the screen, Jev picks the next click local decision models > jaredpalmer/kev (~7.1k): Jev-like models on Qwen, same /v1/systemone wire format > mizorewww/laya-mlx (~6.4k): Laya, the main open Jev-style engine, running on Apple silicon > TheoLeeCJ/SemIf-OpenJev (~4.3k): local semantic ifs from frozen open models, not a TypeSafe project > contrastive-lm/clm (~1.3k): open System One model with a Choice / Noul / Score API > vinnylarouge/jevlike (~1.3k): community trainer and tooling for your own Jev-like model context + skills > tamaratran/fast-jev-compaction (~6.9k): Claude Code plugin, Jev keeps, drops or truncates tool results instead of summarizing context > typesafe-ai/skills (~2.2k): official TypeSafe skill for Claude Code and Codex trading > jarrodwatts/jev-trader (~2.4k): one Jev buy/sell decision per Monad block catalogs > yibie/awesome-jev (~1.7k): the biggest map of Jev projects and discussions > Anil-matcha/awesome-jev-by-typesafe (~851): use cases, patterns and starter code start with jev-ultrafast
0:22

this is f*cking gold 12 open-source repos that plug Jev into real AI work, 550.7k stars combined Jev decides, your LLM writes. these repos are where that split already runs: agents > browser-use/jev-ultrafast (~20.3k): Jev picks the next action + DOM element, a small LLM only types. Zürich to London flights in ~7s > awlevin/typesafe-computer-use (~978): macOS computer use, OCR reads the screen, Jev picks the next click local decision models > jaredpalmer/kev (~7.1k): Jev-like models on Qwen, same /v1/systemone wire format > mizorewww/laya-mlx (~6.4k): Laya, the main open Jev-style engine, running on Apple silicon > TheoLeeCJ/SemIf-OpenJev (~4.3k): local semantic ifs from frozen open models, not a TypeSafe project > contrastive-lm/clm (~1.3k): open System One model with a Choice / Noul / Score API > vinnylarouge/jevlike (~1.3k): community trainer and tooling for your own Jev-like model context + skills > tamaratran/fast-jev-compaction (~6.9k): Claude Code plugin, Jev keeps, drops or truncates tool results instead of summarizing context > typesafe-ai/skills (~2.2k): official TypeSafe skill for Claude Code and Codex trading > jarrodwatts/jev-trader (~2.4k): one Jev buy/sell decision per Monad block catalogs > yibie/awesome-jev (~1.7k): the biggest map of Jev projects and discussions > Anil-matcha/awesome-jev-by-typesafe (~851): use cases, patterns and starter code start with jev-ultrafast

NO1ennn

41,408 görüntüleme • 7 gün önce

If you didn't feel the ongoing revolution, here is my second project I built with jev. Your software is drastically outdated. It contains a lot of instructions your CPU executes one by one. Why if we can simply ask Jev for the next instructions to execute Introducing Jevassembler! It is a new approach to execute something on CPU. You don't need to wait for code to be written, you don't need to compile anything and YOU DON'T NEED CODE. You just give it a task and Jev predicts the next instruction to execute. In runtime. who needs compilers if you have AI
0:28

If you didn't feel the ongoing revolution, here is my second project I built with jev. Your software is drastically outdated. It contains a lot of instructions your CPU executes one by one. Why if we can simply ask Jev for the next instructions to execute Introducing Jevassembler! It is a new approach to execute something on CPU. You don't need to wait for code to be written, you don't need to compile anything and YOU DON'T NEED CODE. You just give it a task and Jev predicts the next instruction to execute. In runtime. who needs compilers if you have AI

Dmitriy Kovalenko

224,570 görüntüleme • 14 gün önce

ANTHROPIC LEAKED A FILE THEIR LEAD ENGINEER SPENT 4 YEARS BUILDING AT A COST OF $3.2M - ONE SUPER AGENT WITH JEV HOLDS A BUSINESS DOING $2.4M A YEAR the agent costs $0, and in month one it's already pulling $100K+ read → decide → build → ship → watch → back to reading 24 cycles a day, and each one starts exactly where the last one stopped it doesn't sleep, doesn't forget and never asks what to do next in one night it runs more cycles than a team closes in a quarter JEV holds the context, the budget and the stop condition between hours - without it every cycle would start from zero it picks one change an hour, not twenty - which is exactly why nothing breaks if things get worse it rolls back on its own, no meeting and no explanation the price of the loop doesn't grow with the revenue: it's the same at $0 and at $200,000 a month $2.4M a year is 669 customers, and that's only true while all 669 keep paying every month one agent is one point of failure: the night the loop stopped, nobody noticed until morning it ships the changes, it doesn't find the customers - that part is still yours save this and paste it into Claude Code - let it build you this loop ↓
0:59

ANTHROPIC LEAKED A FILE THEIR LEAD ENGINEER SPENT 4 YEARS BUILDING AT A COST OF $3.2M - ONE SUPER AGENT WITH JEV HOLDS A BUSINESS DOING $2.4M A YEAR the agent costs $0, and in month one it's already pulling $100K+ read → decide → build → ship → watch → back to reading 24 cycles a day, and each one starts exactly where the last one stopped it doesn't sleep, doesn't forget and never asks what to do next in one night it runs more cycles than a team closes in a quarter JEV holds the context, the budget and the stop condition between hours - without it every cycle would start from zero it picks one change an hour, not twenty - which is exactly why nothing breaks if things get worse it rolls back on its own, no meeting and no explanation the price of the loop doesn't grow with the revenue: it's the same at $0 and at $200,000 a month $2.4M a year is 669 customers, and that's only true while all 669 keep paying every month one agent is one point of failure: the night the loop stopped, nobody noticed until morning it ships the changes, it doesn't find the customers - that part is still yours save this and paste it into Claude Code - let it build you this loop ↓

Sprytix

10,185 görüntüleme • 11 gün önce

He is 18 teaching AI at Stanford making $2.2M on agents - and in 60 minutes revealed how to repeat it from zero: 00:30 - 5% who build agents will replace the 95% who just use them 38:33 - Jev Engineering is the only thing you need to make $2.2M on an agent 52:47 - Claude + Jev 10x cheaper and faster right now after watching I built my first agent with Jev in 15 minutes and sold it to a million dollar company for $100k: save & watch - the article below shows how to use Jev Engineering to make Claude 10x cheaper and build a $2.2M agent.
1:11:34

He is 18 teaching AI at Stanford making $2.2M on agents - and in 60 minutes revealed how to repeat it from zero: 00:30 - 5% who build agents will replace the 95% who just use them 38:33 - Jev Engineering is the only thing you need to make $2.2M on an agent 52:47 - Claude + Jev 10x cheaper and faster right now after watching I built my first agent with Jev in 15 minutes and sold it to a million dollar company for $100k: save & watch - the article below shows how to use Jev Engineering to make Claude 10x cheaper and build a $2.2M agent.

Noisy

13,207 görüntüleme • 11 gün önce

Jev Engineering turns one agent chain into a decision graph that can reroute itself and moves the expensive model out of every decision loop. the important part in this setup isn’t the number of agents. it’s that execution doesn’t follow one fixed path. and up to 193x faster and 444x cheaper in tests. every result can change what happens next: state → Jev decision → branch → specialist agent → result → score → reroute and Jev Engineering sits above that graph deciding: which route stays alive → which specialist gets control → when two branches should merge → when a result needs another pass → when the goal is good enough to stop by the end of the run: 5,400 executions → 0.93 goal score → $0.020 decision cost that’s why Jev Engineering is more than model routing. it’s the control layer that keeps a changing agent graph pointed at one objective. full breakdown below ↓
0:39

Jev Engineering turns one agent chain into a decision graph that can reroute itself and moves the expensive model out of every decision loop. the important part in this setup isn’t the number of agents. it’s that execution doesn’t follow one fixed path. and up to 193x faster and 444x cheaper in tests. every result can change what happens next: state → Jev decision → branch → specialist agent → result → score → reroute and Jev Engineering sits above that graph deciding: which route stays alive → which specialist gets control → when two branches should merge → when a result needs another pass → when the goal is good enough to stop by the end of the run: 5,400 executions → 0.93 goal score → $0.020 decision cost that’s why Jev Engineering is more than model routing. it’s the control layer that keeps a changing agent graph pointed at one objective. full breakdown below ↓

Ricker

13,895 görüntüleme • 10 gün önce

I can't believe this is f*cking free how to build your first AI agent (full guide, with a Jev decision layer) a year ago I burned two weeks on my first agent. this guide gets you there in an afternoon in the right hands it makes one builder ship like a small team:
0:25

I can't believe this is f*cking free how to build your first AI agent (full guide, with a Jev decision layer) a year ago I burned two weeks on my first agent. this guide gets you there in an afternoon in the right hands it makes one builder ship like a small team:

Mr. Buzzoni

58,975 görüntüleme • 2 gün önce

Jev Engineering is what lets one decision layer control hundreds of agent paths without turning the system into chaos. and up to 193x faster and 444x cheaper in tests. it’s deciding: → which model gets called → which tool gets access → which result survives that’s what the video is showing. one state enters. Jev turns it into structured decisions. those decisions fan out across dozens of routes, agents and tools. then everything collapses back into one verified state. so instead of: LLM → agent → tool → another LLM → another guess you get: state → Jev decision layer → parallel routes → execution → verification → next state that’s the point of Jev Engineering: more parallelism without giving every branch permission to improvise. full breakdown in the article below ↓
0:34

Jev Engineering is what lets one decision layer control hundreds of agent paths without turning the system into chaos. and up to 193x faster and 444x cheaper in tests. it’s deciding: → which model gets called → which tool gets access → which result survives that’s what the video is showing. one state enters. Jev turns it into structured decisions. those decisions fan out across dozens of routes, agents and tools. then everything collapses back into one verified state. so instead of: LLM → agent → tool → another LLM → another guess you get: state → Jev decision layer → parallel routes → execution → verification → next state that’s the point of Jev Engineering: more parallelism without giving every branch permission to improvise. full breakdown in the article below ↓

Ricker

44,743 görüntüleme • 12 gün önce

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.
0:29

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.

Akshay 🚀

119,118 görüntüleme • 10 gün önce