Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

How does Jev work? Jev takes two things: your input and an output schema. The schema gives the structure of the answer you want. I send an email. My schema asks for two fields: is spam, and a category from marketing, finance, or spam. Jev returns: - is spam:...

startupideaspod's profile picture

The Startup Ideas Podcast (SIP) 🧃

48,152 subscribers

12,032 Aufrufe • vor 5 Tagen •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

3 Kommentare

Profilbild von Joshua Pi'Rwot
Joshua Pi'Rwotvor 5 Tagen

Writing the schema is where most of the real work sits, and it is easy to underrate. Once you can state the shape of a correct answer field by field, you have already decided what counts as correct. The model filling it in is doing the easier half. When output quality is poor it is usually because the schema was vague, and the prompt gets blamed for it. It also makes failures easier to spot. A missing field shows up immediately, where a weak paragraph can sit there for weeks with everyone assuming it is fine.

Profilbild von Jay
Jayvor 5 Tagen

the schema is doing the real work here

Profilbild von AI Mastery Guide
AI Mastery Guidevor 5 Tagen

Finally someone explains Jev simply

Ähnliche Videos

What does it cost to sort 1,700 emails with Jev? I gave JEV each full email object: - Subject - body - sender No special changes. Jev sent back 4 values for each email: - Category: work, shopping, finance, security - Priority: low to urgent - Spam score: a percentage - Reply score: how much the email needs a reply from me One user wrote that their account had a violation. JEV gave it a 90% reply score. The run used 4.2 million input tokens and 500,000 output tokens. The final cost was 18 cents. The total time was 12 seconds.
2:48

What does it cost to sort 1,700 emails with Jev? I gave JEV each full email object: - Subject - body - sender No special changes. Jev sent back 4 values for each email: - Category: work, shopping, finance, security - Priority: low to urgent - Spam score: a percentage - Reply score: how much the email needs a reply from me One user wrote that their account had a violation. JEV gave it a 90% reply score. The run used 4.2 million input tokens and 500,000 output tokens. The final cost was 18 cents. The total time was 12 seconds.

The Startup Ideas Podcast (SIP) 🧃

11,588 Aufrufe • vor 6 Tagen

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 Aufrufe • vor 5 Tagen

Someone said: I have created 5 Gmail accounts and Yahoo Mail but all the cold emails I send goes to the spam folder. Why is this so? My Answer: Did you test your cold email for spam triggers before sending? Before you send your next cold email, check if there are spam words. Words as simple as "For You" can send your email to spam folder No need for stories Let me show you how to Test your draft email for spam triggers Even your chatgpt and clause emails are not safe. Test it first Thank me later
17:44

Someone said: I have created 5 Gmail accounts and Yahoo Mail but all the cold emails I send goes to the spam folder. Why is this so? My Answer: Did you test your cold email for spam triggers before sending? Before you send your next cold email, check if there are spam words. Words as simple as "For You" can send your email to spam folder No need for stories Let me show you how to Test your draft email for spam triggers Even your chatgpt and clause emails are not safe. Test it first Thank me later

Richard U. | Web Developer

23,190 Aufrufe • vor 1 Monat

HOW TO STOP YOUR COLD EMAIL FROM GOING TO SPAM. (100% WORKING) Someone asked: All my cold emails are going to Spam folder. How can I solve this permanently? Is it possible? My answer: We can always make sure our cold emails do not get to spam. Infact in this video I will show you what I do and how I avoid spam folder. If you try this method fully and your email still goes to spam, just pack your bags to your village or go and beg your village people... This is a sure method, I guarantee you If your email still enter spam after this, then cold email is not for you. Watch this video Thank me later
19:37

HOW TO STOP YOUR COLD EMAIL FROM GOING TO SPAM. (100% WORKING) Someone asked: All my cold emails are going to Spam folder. How can I solve this permanently? Is it possible? My answer: We can always make sure our cold emails do not get to spam. Infact in this video I will show you what I do and how I avoid spam folder. If you try this method fully and your email still goes to spam, just pack your bags to your village or go and beg your village people... This is a sure method, I guarantee you If your email still enter spam after this, then cold email is not for you. Watch this video Thank me later

Richard U. | Web Developer

94,851 Aufrufe • vor 1 Monat

Jev Founder, Diogo Almeida (ex-OpenAI): "The next era is not the Claude Code era. Claude Code is still part of the assistance era - Jev is the next step Jev is x200 faster, x400 cheaper and has 0 hallucination. This is what comes after RLHF" In 17 minutes he explains why every model you use has a human-shaped flaw baked into it and why Jev is better worth more than a $500 Claude Code engineering course watch today, then read how to actually boost yourself x100 with Jev in the post below
17:33

Jev Founder, Diogo Almeida (ex-OpenAI): "The next era is not the Claude Code era. Claude Code is still part of the assistance era - Jev is the next step Jev is x200 faster, x400 cheaper and has 0 hallucination. This is what comes after RLHF" In 17 minutes he explains why every model you use has a human-shaped flaw baked into it and why Jev is better worth more than a $500 Claude Code engineering course watch today, then read how to actually boost yourself x100 with Jev in the post below

Codez

189,392 Aufrufe • vor 6 Tagen

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 Aufrufe • vor 4 Tagen

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓
0:24

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

194,422 Aufrufe • vor 3 Tagen

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. agent-desktop Desktop automation. Read the system's accessibility tree, judge which button, menu, or input field to click next. 2. typesafe-mario Have Jev play Super Mario. No screenshots—just read the structured state in the emulator's RAM, then decide to run, jump, or dodge. 3. jev-drone Use Jev to control a drone. The underlying flight control still handles stability and safety; Jev just does higher-level judgments like climbing, braking, and navigating obstacles. 4. OneVOneJev 1v1 FPS in the browser. Every decision tick, judge movement, view angle, aiming, firing, and jumping. 5. jev-trader High-frequency market making on Monad testnet. Jev judges the next buy or sell based on spreads and trade direction, with model latency around 81ms. 6. Prism Doesn't directly have Jev place orders. It judges states like toxic flow, market pressure, mean reversion, etc., then hands off to the original strategy. 7. neo4jev Stuff Jev into a knowledge graph. At each node, judge the most worthwhile edge to take next, then follow it all the way. 8. jev-curate Use Jev to screen training data. For JSONL / Parquet, first judge quality, relevance, and risk, then decide which ones go into the next training round. 9. Canny Prevents Coding Agents from stubbornly claiming they're done. Look at tool outputs, code diffs, and test results, then judge if the completion claim is reliable. 10. killmyidea Input a startup idea, and Jev scores it from multiple angles, finally giving you KILL, FIX, or SHIP. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓
0:24

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. agent-desktop Desktop automation. Read the system's accessibility tree, judge which button, menu, or input field to click next. 2. typesafe-mario Have Jev play Super Mario. No screenshots—just read the structured state in the emulator's RAM, then decide to run, jump, or dodge. 3. jev-drone Use Jev to control a drone. The underlying flight control still handles stability and safety; Jev just does higher-level judgments like climbing, braking, and navigating obstacles. 4. OneVOneJev 1v1 FPS in the browser. Every decision tick, judge movement, view angle, aiming, firing, and jumping. 5. jev-trader High-frequency market making on Monad testnet. Jev judges the next buy or sell based on spreads and trade direction, with model latency around 81ms. 6. Prism Doesn't directly have Jev place orders. It judges states like toxic flow, market pressure, mean reversion, etc., then hands off to the original strategy. 7. neo4jev Stuff Jev into a knowledge graph. At each node, judge the most worthwhile edge to take next, then follow it all the way. 8. jev-curate Use Jev to screen training data. For JSONL / Parquet, first judge quality, relevance, and risk, then decide which ones go into the next training round. 9. Canny Prevents Coding Agents from stubbornly claiming they're done. Look at tool outputs, code diffs, and test results, then judge if the completion claim is reliable. 10. killmyidea Input a startup idea, and Jev scores it from multiple angles, finally giving you KILL, FIX, or SHIP. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

334,032 Aufrufe • vor 2 Tagen

sharing an easy way to test DJev (Diffusion Gemma Jev), the next evolution of the incredible jev concept and fully open sourced (model, code, api...) imagine jev but it also has: - native image-input support - native image as options!! - real-time video streaming input - as fast as jev (not with images, 600ms) - same price as jev, but can get even cheaper - using Diffusion Gemma adapted - we are seeing on-par performance but happy to have external validation! It is a research preview made for fun, so don't expect stability and the awesome scaling as jev team has delivered! this was a weekend project :) have fun!
1:30

sharing an easy way to test DJev (Diffusion Gemma Jev), the next evolution of the incredible jev concept and fully open sourced (model, code, api...) imagine jev but it also has: - native image-input support - native image as options!! - real-time video streaming input - as fast as jev (not with images, 600ms) - same price as jev, but can get even cheaper - using Diffusion Gemma adapted - we are seeing on-par performance but happy to have external validation! It is a research preview made for fun, so don't expect stability and the awesome scaling as jev team has delivered! this was a weekend project :) have fun!

David Villalón

40,204 Aufrufe • vor 5 Tagen

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

222,422 Aufrufe • vor 5 Tagen

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.
0:46

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.

Ruben Hassid

167,306 Aufrufe • vor 3 Tagen

Jev Founder, Diogo Almeida (ex-OpenAI): "The next era is not the Claude Code or Codex era, they are still part of the assistance era with human in the loop - JEV is what comes next for LLMs x200 faster, x400 cheaper, 0 hallucination, no human in the loop - that's JEV, this is how LLMs will look like" in 36-minute tech talk, Jev Founder explained why RLHF isn't a thing anymore and how modern LLMs will be built this talk is worth more than a Stanford Machine Learning degree watch today no matter what, then learn how to become a Jev Engineer in the article below
36:14

Jev Founder, Diogo Almeida (ex-OpenAI): "The next era is not the Claude Code or Codex era, they are still part of the assistance era with human in the loop - JEV is what comes next for LLMs x200 faster, x400 cheaper, 0 hallucination, no human in the loop - that's JEV, this is how LLMs will look like" in 36-minute tech talk, Jev Founder explained why RLHF isn't a thing anymore and how modern LLMs will be built this talk is worth more than a Stanford Machine Learning degree watch today no matter what, then learn how to become a Jev Engineer in the article below

Codez

444,060 Aufrufe • vor 5 Tagen

I got a rubik's cube to solve itself with TypeSafe AI 's Jev and it solves it like a person does, 94 moves, not the 22 move optimal solution. Jev isn't an LLM, it just answers one question in ~250ms with a probability. so I put the beginner method in code (the one you'd learn on youtube: white cross, corners, middle layer, yellow layer) and at every step Jev just looks at the cube and picks which case it's in. code checks every pick. ~4 seconds of model time total. video is slowed down so you can read it!
0:34

I got a rubik's cube to solve itself with TypeSafe AI 's Jev and it solves it like a person does, 94 moves, not the 22 move optimal solution. Jev isn't an LLM, it just answers one question in ~250ms with a probability. so I put the beginner method in code (the one you'd learn on youtube: white cross, corners, middle layer, yellow layer) and at every step Jev just looks at the cube and picks which case it's in. code checks every pick. ~4 seconds of model time total. video is slowed down so you can read it!

Paolo Rosson

207,238 Aufrufe • vor 7 Tagen

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:
0:30

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:

Roan

119,605 Aufrufe • vor 4 Tagen

I was also looking into how we can integrate Jev into a real hardware and I built a custom firmware for my keyboard that predicts and highljghts the next key using Jev. Mostly real time. This is not a simple dummy 2kb model that lives in the board. In my project Jev gets context of the current active app on a screen so it can suggest actual vim commands completion! For real. And a real word endings or even phrases. lmao this experiments are getting out of hand this quite cool
0:35

I was also looking into how we can integrate Jev into a real hardware and I built a custom firmware for my keyboard that predicts and highljghts the next key using Jev. Mostly real time. This is not a simple dummy 2kb model that lives in the board. In my project Jev gets context of the current active app on a screen so it can suggest actual vim commands completion! For real. And a real word endings or even phrases. lmao this experiments are getting out of hand this quite cool

Dmitriy Kovalenko

56,086 Aufrufe • vor 4 Tagen

Jev by TypeSafe AI is now on the Venice API, in beta. It answers, it doesn't write. Send it your app's state and typed questions. Get back a typed answer your code can branch on: a probability, a chosen option, or a score on your rubric. No JSON to coax out of a chat model.
0:24

Jev by TypeSafe AI is now on the Venice API, in beta. It answers, it doesn't write. Send it your app's state and typed questions. Get back a typed answer your code can branch on: a probability, a chosen option, or a score on your rubric. No JSON to coax out of a chat model.

Venice

536,864 Aufrufe • vor 6 Tagen

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.
0:31

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

279,042 Aufrufe • vor 3 Tagen

Thanks to Jev, you can now write workflows in plain English and run them instantly like code. I spent the day feeding it descriptions of tasks and it spit out workflows across hundreds of apps faster than I could read them. An agent could do this already, in 30 seconds, for a dollar, differently every run. Jev does it in two seconds, for free, the same way every time.
0:33

Thanks to Jev, you can now write workflows in plain English and run them instantly like code. I spent the day feeding it descriptions of tasks and it spit out workflows across hundreds of apps faster than I could read them. An agent could do this already, in 30 seconds, for a dollar, differently every run. Jev does it in two seconds, for free, the same way every time.

Gil Feig

60,209 Aufrufe • vor 4 Tagen

I built a voice controlled computer-use for my mac using TypeSafe AI's Jev and it's INSANE how fast it is! I can dictate "open the notes app and create..." and the app opens before I even finish my sentence.
0:48

I built a voice controlled computer-use for my mac using TypeSafe AI's Jev and it's INSANE how fast it is! I can dictate "open the notes app and create..." and the app opens before I even finish my sentence.

Andy Gao

648,323 Aufrufe • vor 7 Tagen

Okay so Jev can actually do computer use really well Without any screenshots, or LLMs and no Pixels leave my mac I dont even read the Dom elements A local CoreML model segments every button and UI element on screen. On-device OCR reads the labels. That text is all Jev gets. It returns a probability across those elements and tells me the best one to click. Then it clicks, re-runs detection, and decides again. In a loop until the goal is done. ~90ms per decision. Faster than any LLM computer use I've tried. Blazing fast computer use, without any latency TypeSafe AI is building something really interesting
2:13

Okay so Jev can actually do computer use really well Without any screenshots, or LLMs and no Pixels leave my mac I dont even read the Dom elements A local CoreML model segments every button and UI element on screen. On-device OCR reads the labels. That text is all Jev gets. It returns a probability across those elements and tells me the best one to click. Then it clicks, re-runs detection, and decides again. In a loop until the goal is done. ~90ms per decision. Faster than any LLM computer use I've tried. Blazing fast computer use, without any latency TypeSafe AI is building something really interesting

Milind S

238,797 Aufrufe • vor 7 Tagen