Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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...

208,053 görüntüleme • 1 ay önce •via X (Twitter)

33 Yorum

ZeroTrace AI profil fotoğrafı
ZeroTrace AI1 ay önce

@typesafeai Worth noting the 94 vs 22 gap comes from the scaffold, not the model: the beginner method deliberately constrains the solution space. The real design win is that deterministic code validates each probabilistic pick.

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Yes totally!

Sean Gorsky profil fotoğrafı
Sean Gorsky1 ay önce

@typesafeai

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai A bit paradoxical 🤣

Eric Forbell profil fotoğrafı
Eric Forbell1 ay önce

@typesafeai Actual AI engineers coming out of the woodwork. Love it!

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Thank you! Much appreciated

Ian Nuttall profil fotoğrafı
Ian Nuttall1 ay önce

@typesafeai Now we load Jev into a robot solver and sell it for $50 a pop!

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Hahaha gotta do it now 😎

CryZe profil fotoğrafı
CryZe1 ay önce

@typesafeai This does not seem any better than using an LLM though. An LLM could have written you the exact code to solve it, and it would have cost you nothing.

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai This is a different approach altogether! Of course it coukd be done with an llm but less efficiently!

Zálesák 🇨🇿🇪🇺 profil fotoğrafı
Zálesák 🇨🇿🇪🇺1 ay önce

@typesafeai Incredible. I wonder if someone could make a mixed system that would use Jev for 90% of things but delegate to an LLM when it needed to think longer about a decision, kinda like how humans work.

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai That’s exactly the idea! And how to use it!

JCP profil fotoğrafı
JCP1 ay önce

@typesafeai Gods number is 20, so every Rubik’s cube no matter the position can be solved in 20 moves or less (meaning the 22 move solution can’t be optimal) :)

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Can’t argue with this!

𝗔𝗡𝗘𝗭𝗢 (❖,❖) profil fotoğrafı
𝗔𝗡𝗘𝗭𝗢 (❖,❖)1 ay önce

@typesafeai How did you guys get access?

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Just signed up to the waitlist

Dhruva Goyal ☤ profil fotoğrafı
Dhruva Goyal ☤1 ay önce

@typesafeai So there is no lookahead / test time compute sort of thing happening here, its a direct general purpose classifier?

1223334444555554444333221 profil fotoğrafı
12233344445555544443332211 ay önce

@typesafeai that just sounds like coding a rubik's solver with extra [pointless] steps :)

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai The interesting part is that it uses the same approach a person would now what a computer would do

DreadBread profil fotoğrafı
DreadBread1 ay önce

@typesafeai You gave jev an algorithm and it executed it. That‘s orders of magnitudes slower that compiling the algorithm to machine code and executing it directly.

c(x) profil fotoğrafı
c(x)1 ay önce

@typesafeai Superb.

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Thank you! It’s a great new tool!

c(x) profil fotoğrafı
c(x)1 ay önce

@typesafeai Indeed! 👍

Chris | Agent OverMind ⚡ profil fotoğrafı
Chris | Agent OverMind ⚡1 ay önce

@typesafeai When is this available via api!?!??!

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai You can sign up to the waitlist. I got access in a day or so

Chris | Agent OverMind ⚡ profil fotoğrafı
Chris | Agent OverMind ⚡1 ay önce

@typesafeai Ty

Ahmet profil fotoğrafı
Ahmet1 ay önce

@typesafeai Can you play a game of chess with Jev?

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai Definitely!

Vishesh Baghel profil fotoğrafı
Vishesh Baghel1 ay önce

@typesafeai Really cool stuff. There are many algos already present. Does jev beat them? Recently built this with jev as well

Shane profil fotoğrafı
Shane1 ay önce

@typesafeai Reminds me of my childhood. So fun.

Paolo Rosson profil fotoğrafı
Paolo Rosson1 ay önce

@typesafeai One of the best childhood activities!!

ralph profil fotoğrafı
ralph1 ay önce

@typesafeai That's not impressive Im calculating n reductions in the delete path in under 4 minutes - Jev is terrible I looked at it who ever engineered it they're clueless wouldn't even listen to them - this is like sharing an md file and acting like you won.

Sahibzada Allahyar profil fotoğrafı
Sahibzada Allahyar1 ay önce

@typesafeai GLiNER can do the same agentic decision making tasks like Jev while being local, free and open weights. it's so lightweight it'll run on a laptop.

Benzer Videolar

Jev is quietly taking over the agent stack. If you already have a Jev API key and don't know what to build first, steal this checklist: 1. jev-opus Runs Claude Code on Opus 5.5 and asks Jev before every call how much effort the next step needs: low, medium or high. Code enforces the floors and ceilings, and the prompt cache stays intact. 2. jev-belay A Claude Code Stop hook that won't trust "done" without evidence. If files changed and nothing passed since, one Jev call checks the transcript before the agent is allowed to stop. 3. jev-skill-router On every prompt, Jev picks one skill from everything you have installed, or none. It starts in shadow mode and only logs, so you see its picks before you trust them. 4. codex-jev-router Jev picks the model and reasoning effort for each Codex subagent. When Jev is unsure, it falls back to Sol. 5. jev-commit A pre-commit hook. One Jev call checks whether your commit message actually matches the staged diff and flags debug leftovers and unmentioned work. 6. is-malicious Scans source, config, build and CI files with Jev and points at the suspicious lines before the code ever runs. 7. jegrep Semantic grep in Rust. Jev scores your files with probabilities, no embedding index and no background daemon. 8. jev-scout An MCP server that scores every search query, result and fetched page your agent touches for relevance and credibility, with a live decision dashboard. 9. hunch Probabilistic control flow for Ruby. if Hunch.likely?("fraudulent", given: order) branches on a typed Jev answer. 10. pytest-jev Write plain-English claims about your output, and the test passes only when Jev clears every claim above 0.8. Copy any of these Jev builds, then read the full Jev setup below ↓

Chen

29,260 görüntüleme • 1 ay önce

Jev came out and people instantly started doing dumb sh*t with it Minecraft, Mario, a Tesla car, a real phone, a trading account and basically said: "your call." here's what happened: > minecraft-agent Jev beat Minecraft. a bigger model plans the route, Jev picks every single move: mine, craft, fight. 8:43 run. 131 decisions. killed the dragon with exploding beds. > > jevpilot a Tesla-style autopilot in a browser driving sim. Jev picks steering + speed up to 4 times a second. > > typesafe-mario Jev plays the original Super Mario. it gets Mario's position, enemies and terrain as data and presses one of 7 buttons. no screenshots. no vision. > > mobile-jev Jev drives a real Android phone. opened Uber, typed the route, got to payment. ~9 actions. ~21 seconds. > > jev-voice-browser talk to your browser. Jev clicks. it often acts before you finish the sentence. ~300ms per word. whole demo cost ~1 cent. > > jev-trade 5 coins on Hyperliquid. every second Jev picks: long or short -> open, close or hold. > > youtube-sponsor-detection "this video is sponsored by..." -> skipped. under a cent per hour of video. > > unclutter Jev looks at a page and hides the ads, cookie popups and newsletter boxes. remembers each site, so the next visit costs zero API calls. > > jev-pruner your 76,000-character log -> 4,000 characters before Claude reads it. errors stay. noise goes. > > fast-jev-compaction Claude Code usually summarizes old context and loses details. here Jev just decides what to keep and what to drop. nothing gets rewritten. > and here's the pattern: none of these need Jev to write anything. they need it to look and pick: MINE / CRAFT / FIGHT LEFT / RIGHT / JUMP TAP / TYPE / SCROLL LONG / SHORT / HOLD AD / NOT AD KEEP / DROP that's the whole thing. the big model plans. Jev picks. code does the rest.

kiosa

64,678 görüntüleme • 1 ay ö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

NO1ennn

18,445 görüntüleme • 1 ay önce

this is pure f*cking treasure Engineer at TypeSafeAI just mapped 389 public Jev builds in one list: skills, MCP servers, SDKs, agents, benchmarks and guides ROUTING > jev-router sends every Claude Code task to the cheapest model that can do it > Switchboard picks the model and reasoning effort per task, then keeps it stable so the prompt cache survives > jev-oncall triages alerts: 418 ms p50, $0.04 per 1,000 alerts GUARDRAILS > jev-axi gates shell commands for Claude Code and Codex, 44/44 on its labeled set > hermes-jev-approvals: 8.7x faster approvals, 4.4x fewer prompts to the user > Sniff Test lints AI slop out of your writing at 182 ms a paragraph AGENTS > Jev Ultrafast: Jev picks every click, a small LLM only types > fast-jev-compaction scores your context instead of summarizing it > jev-browser-use reports 5 to 10x faster browser runs inside Codex SEARCH & RAG > jev-retrieval placed 2nd of 90 models on a reranking leaderboard > jevsearch: 83% Hit@1 against 41% for keyword search alone SDKs & MCP > clients for Swift, Go, Rust, Kotlin, Ruby, Elixir, .NET, Laravel and Spring > MCP servers for Claude Code, Cursor and Codex > Jev inside SQLite, DuckDB and Postgres, straight from SQL EVALS > pytest-jev checks LLM replies in 5.3 s where Claude took 27.1 s > a medical hallucination check at 92.9% accuracy, 204 ms, $0.03 per 1,000 OPEN MODELS > Laya answers in one ~35 ms forward pass > kev trains and runs on a MacBook GAMES, ROBOTS, TRADING > Jev plays Mario, Pokemon and chess > it drives a robot arm and a drone > it trades on Monad with 81 ms decisions 389 builds. one decision layer. go steal the ones you need

NO1ennn

25,798 görüntüleme • 1 ay ö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 ↓ ↓

Hanako

29,894 görüntüleme • 1 ay ö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 ↓

Hanako

44,263 görüntüleme • 1 ay önce

People already built a browser agent, a Claude Code bridge and a LangGraph router on top of Jev. Here are all 10 repos. If you have API access and don't know where to start, save this: 1. jev-browser Real browser control through MCP, CLI or as a library. At every step Jev answers two things: which element to touch, and whether the goal is done or the run is stuck. > 2. jev-browser-agent Picks the operation and the target in a single request, around a second per step. Anything under 0.6 confidence goes up to a bigger model or back to you. > 3. typesafe-jev-bridge OpenAI-compatible bridge with zero dependencies. Typed yes/no, choice and score answers inside Claude Code, Cursor, Cline or any OpenAI SDK, via CLI or HTTP. > 4. pilot-typesafeai-jev Jev wired into LangGraph and Deep Agents. Three questions in one request, plain code chooses the route, and the chat model only spends tokens on the route that won. > 5. building-with-jev-skill Agent skill for writing code that calls Jev. How to phrase questions, structure state, set thresholds, and debug a question that keeps answering wrong. > 6. jev-skill Guided setup and eval workflows. Checks what's installed without changing anything, never swaps your provider behind your back, never makes up probabilities. > 7. awesome-jev (yibie) What people actually shipped with Jev, sourced and sorted by category, with the limitations written down for each entry. > 8. awesome-typesafe-jev SDKs, live demos, agent tools and independent evals. Shows where every vendor number comes from. > 9. awesome-jev-by-typesafe Use cases, patterns and starter code backed by evidence. The 70 to 500 ms latency figure is labeled vendor-reported, not measured. > 10. awesome-jev (cobanov) Biggest catalogue so far: SDKs for Go, Java and JS, MCP connectors, guardrail experiments and studies. > Copy these complete Jev blueprints - then read full Jev setup below ↓

Asteri

16,629 görüntüleme • 1 ay önce

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

204,901 görüntüleme • 1 ay önce