Loading video...

Video Failed to Load

Go Home

JEV + Opus 5.5 is not fair for web design… Every section you scroll through is re-designed - 27 times in 40 seconds How it works: 1. a section scrolls into view 2. Jev returns one typed decision in ~0.1s { layout, type, palette, drop, p } 3. Section...

77,842 views • 13 days ago •via X (Twitter)

11 Comments

Robu's profile picture
Robu13 days ago

27 redesigns in one scroll is less web design, more a slot machine with CSS loaded

Kai Lennox's profile picture
Kai Lennox13 days ago

27 redesigns in 40 seconds is stupid 😭

0xSlyth's profile picture
0xSlyth13 days ago

27 redesigns in 40 seconds is next level

why's profile picture
why13 days ago

Splitting the quick layout decisions from the actual section writing seems like a smart way to keep iteration fast without asking the model to do everything at once.

Emma Rodriguez's profile picture
Emma Rodriguez13 days ago

27 times in 40 seconds is just stupid 😭

AI Studio's profile picture
AI Studio13 days ago

Generative Design alle 0,1 Sekunden neu zu rechnen ist oft Brute-Force statt Handwerk. Erst Ziel, Randbedingungen und Prüfkriterien sauber definieren — dann automatisieren.

Ashik's profile picture
Ashik13 days ago

Fun demo, but the number I'd want is how many of the 27 you'd actually ship. Generating is solved. Choosing is the job now.

ALEXYZ's profile picture
ALEXYZ13 days ago

one typed decision point one seconds is wild

Benjnr's profile picture
Benjnr13 days ago

This is wonderful

Brjan | AI Builder's profile picture
Brjan | AI Builder13 days ago

27 redesigns in 40 seconds sounds like a rapid-fire workflow but could overwhelm users

Jon Berry's profile picture
Jon Berry12 days ago

Called it.

Related Videos

JEV + OPUS 5.5 IS INSANE FOR BUILDING A COMPANY BRAIN I pulled the whole architecture out of the TypeSafe and Anthropic docs and packed it into a 14-page PDF the 10 steps: 1. meet the pair > Opus 5.5 thinks, Jev decides, your code holds the branch 2. stop asking a text generator for a yes or no > Jev returns a typed answer with a calibrated probability in 0.44s for $0.00035 3. ask everything at once > Choice, Score and Noul run in parallel, so the fourth question costs almost nothing 4. branch on the number > 0.999 goes straight into the if statement. ~99% of turns end right here 5. stop routing blind > Opus 5.5 to Sonnet and back costs 5.84 against 3.32 for staying on 5.5 6. keep one context warm > cache reads at $0.20 per Mtok are 20x cheaper than a fresh load 7. escalate the hard part > the toughest 1% goes to Opus 5.5 with 1M context and 66.4% on Terminal-Bench 4.0 8. score every chunk on every query > keep whole, summarize or drop. the context gets rebuilt each turn 9. gate the actual command > every bash call gets classified before it runs, inside your own code 10. judge 100% of runs > $3.50 a day for 10,000 traces, and it matched the human label on all 500 decisions the result: a while loop that paid a frontier model for every tiny call turns into a brain that spends a fraction of a cent to notice and pays properly only when it has to think the person who brings this into their team walks into the budget meeting with the AI bill cut and the output up the PDF maps the company brain. the loop side of it - how Jev takes a Claude bill from $765 to $3 a month - is in the article below ↓

Mr. Buzzoni

103,282 views • 11 days ago

this is pure f*cking treasure Claude Code tip: once Opus 5.5 is your main model, stop leaving Fable 5.1 sitting idle and stop burning Opus tokens on tasks Sonnet 5.5 can swarm put it on call with /goal claude --auto-mode "/goal all tests pass and lint is clean" Opus 5.5 keeps writing the code in auto mode Sonnet 5.5 swarms the routine work at medium Fable 5.1 inspects the full transcript and only speaks up at the turn boundary: → not yet met: am I drifting from acceptance criteria? → met: do the tests, diffs, and lint hold? → impossible: am I chasing an unreachable state? Fable grades. Opus ships JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or halt) go to JEV in under 16ms, and the big models only see the ones that split — the full tree > Opus 5.5 on high runs the main session > worker edits and patches code on Sonnet 5.5 > explorer indexes AST maps and call sites on Sonnet 5.5 > verifier runs tests and linters on Sonnet 5.5 > all three subagents on medium effort > Fable 5.1 on call as the Stop hook evaluator > JEV routes micro-forks under 16ms paste the tree and this prompt into Claude Code ↓ "Reconfigure my Claude Code setup around this tree: 1. Set the main session to Opus 5.5 on high effort with auto mode enabled. 2. Put Fable 5.1 on call as a session-scoped evaluator attached to the Stop hook: - Read-only transcript evaluation with zero tool calls - Three structured outcomes: not yet met (with steering notes), met (auto-clear), and impossible (abort early) 3. Spawn Sonnet 5.5 subagents on medium effort for worker, explorer, and verifier roles. Defer goal checks while background tasks run. 4. Route fast deterministic forks (tool resolution, path selection, auto-retries) through JEV. 5. Add one rule to CLAUDE.md: run long tasks with: claude --auto-mode \"/goal \" Show me every configuration change as a diff first. No edits until I say go." ↳

mirku

40,611 views • 2 days ago

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 views • 14 days ago

this is pure f*cking treasure Netflix engineers posted 20 GitHub repos that turn your Opus 5.5 into a f*cking motion empire: built for Opus 5.5 1. claude-motion: taste, checks its own frames, sound written in code. the author built it for Opus 5.5 2. claude-motion-design: HTML, Playwright and ffmpeg, no Remotion. the demo was made on Opus 5.5 3. motion-graphics-skills: 13 skills for launch videos. the README tells you to run it on Opus 5.5 4. claude-remotion-skill: a Remotion editor from one prompt. captions, B-roll, sound 5. klik-anim-skill-creation: the laws of animation and camera, built on Opus 6. hyperframes-motion-reel-skill: a showreel cut to the beat at 120 BPM, on HyperFrames 7. product-launch-motion: a full launch film. voice-over, camera, color grade 8. animate: a short clip in one canvas file, storyboarded as it goes 9. motion-design-skills: timing, color, typography, logos, Remotion 10. hyperframes-student-kit: 14 skills and 406 motion graphics cards the engines these skills render with 11. hyperframes: HTML to MP4. the one almost everyone installs 12. remotion: video written in React 13. remotion skills: the official Remotion skills for your agent 14. GSAP: the timelines HyperFrames runs on. skills: npx skills add greensock/gsap-skills taste and everything around it 15. motion-design-skill: motion principles that work with any engine 16. awesome-motion-design-agent-skills: a map of GSAP, Remotion, Lottie and Rive skills 17. motion-graphics: B-roll built straight from your transcript 18. motion-dev-animations-skill: web animation on not video 19. motion: Motion itself, formerly Framer Motion 20. lottie-web: when you need Lottie, not MP4 the stack in one line: Opus 5.5 writes the code, a skill sets the timing and the camera, an engine renders the MP4. check each repo before you install. save this.

NO1ennn

281,797 views • 1 day ago

Jev just became the fastest-adopted model in AI history. here's what people already built with it 1. jev-ultrafast - the browser agent that picks every click itself, only calling a text model when it actually needs to type something. found real flight results in 7 seconds for $0.0039. 16,758 stars 2. jev-trader - real trading bot placing live limit orders on Monad every 300ms block, judged by Jev alone. 1,911 stars 3. jev-usecases - production security-operations harness where Jev triages incidents and gates every escalation behind a confidence cutoff before anything touches real infrastructure. zero false escalations in the committed test set 4. tax-doc-classifier - sorts real IRS tax forms with 100% strict accuracy across 261 forms, at roughly $0.001 a page 5. jev-drone - a simulated quadrotor clears a five-station obstacle course by camera alone, Jev judging the situation twice a second 6. killmyidea - describe your startup idea, Jev scores it from every angle, then hands back kill, fix, or ship in seconds, not days 7. jev-curate - streams Parquet and JSONL rows through typed judgments at 1,500+ rows a second, keeping only what clears the bar 8. pg-jev - a PostgreSQL extension that lets you ask your own database tables plain-English questions and get a real answer back, no SQL required eight repos. zero generated words. every single one returns a typed answer against a question someone already defined full setup below, then run the three-question test from the article before you build a ninth

rvaniaaa

85,773 views • 15 days ago

WHAT A TREASURE! TypeSafe's JEV and OpenAI’s OPUS 5.5 + Dots in single system making 100,000,000,000 decisions in 5 minutes. the spider only had to move 96 times. this is an MIT verified stack. while most AI stacks send every decision through the same pipe: something comes in, the biggest model looks at it, and the biggest model answers. it's expensive, slow, and 99.9% of the time it's overkill. i split it into a brain and a spider instead. here's the breakdown: 1. the brain: Jev - a 5,800-node mesh that never sleeps. every decision is a spike of activation spreading across it, one decision every 3 nanoseconds. 100 billion decisions in 5 minutes. no queue, no waiting for anyone to press run. → lesson: the cheap, fast layer should make almost every decision. that's the whole point of it. 2. the spider: Opus 5.5 - it doesn't read the stream. it walks the brain and only goes where activity is hot. it plants its legs on the nodes, probes them and carries the result. 96 probes in 5 minutes. 4 failed and were retried. → lesson: the frontier model shouldn't see everything. it should know where to look. 3. the Dots agents: Echo, Sprout, Pocket, Stella - ingest, train, store, rank. they never touch the raw stream. they only act on what the spider brings them. 31 deliveries, every one tied to a real probe. → lesson: downstream agents work best on curated input, not raw firehose. 4. you - you read one dashboard and a summary. the math: 100,000,000,000 decisions → 96 probes → 31 deliveries → 1 screen. the question that changed how i build these: not "how smart is the model?" but "how rarely does it need to move?" i'm breaking down one AI stack like this every week. if your team still routes every decision through the biggest model, show this to whoever pays the API bill. would you trust a 3-nanosecond decision to tell your most expensive model where to look? why or why not?

deezzex

25,385 views • 3 days ago

this is unreal f*cking gold for Jev builders 20 repos people are building on Jev right now. browser agents, context tools, trading bots, even a drone 1. JEV-Ultrafast - a browser agent built for speed ↳ 2. Fast-JEV-Compaction - squeezes your context down ↳ 3. JSON-Render - UI generated on the fly ↳ 4. Typesafe-MCP - plugs Jev into any client ↳ 5. JEV-MCP - a toolkit for judgment calls ↳ 6. Semdecide - a classifier right in your terminal ↳ 7. JEV-Codex-Router - sends every task to the model that fits it ↳ 8. Winnow - clears the junk out of your context ↳ 9. JEV-Review - sorts code reviews by what needs eyes first ↳ 10. Blink - finds your way around any repo ↳ 11. Agent-Desktop - runs your desktop for you ↳ 12. Typesafe-Mario - an agent playing Super Mario ↳ 13. JEV-Drone - flies a drone ↳ 14. OneVOneJev - a shooter in your browser ↳ 15. JEV-Trader - high-frequency market making ↳ 16. Prism - spots liquidity signals ↳ 17. Neo4Jev - walks a knowledge graph ↳ 18. JEV-Curate - screens training data ↳ 19. Canny - confirms a task is really finished ↳ 20. KillMyIdea - scores a startup idea before you sink time into it ↳ start where your work is: > coding -> JEV-Review, Blink, Canny, JEV-Codex-Router > context -> Fast-JEV-Compaction, Winnow > automation -> JEV-Ultrafast, Agent-Desktop > clients and tools -> Typesafe-MCP, JEV-MCP, Semdecide > UI -> JSON-Render > trading -> JEV-Trader, Prism > data -> Neo4Jev, JEV-Curate > founders -> KillMyIdea > for fun -> Typesafe-Mario, OneVOneJev, JEV-Drone pick one, build on it this week, and you'll be the person on your team who actually knows Jev engineering when it gets asked for

Mr. Buzzoni

11,667 views • 9 days ago

THIS IS F*CKING INSANE, I ADDED A CRAWLER TO JEV + MY GROK BOTS AND SLEPT, MY $100 RESTART IS NOW $12,161 AFTER 3 NIGHTS everyone on my timeline built a web crawler this week most of them just scrape headlines a crawler is a bot that reads web pages for you i plugged mine into the setup i already had the crawler reads, Jev decides, my Grok bots trade Jev is the AI that answers every question yes or no, under a second, under a cent honestly the crawler alone is a toy, Jev is what turns reading into a trade a coin called CRAWL launched at 10pm at $46K, by 11pm it was $2.05M what the three of them did while i slept: → crawler went through 88 fresh coins, Jev kept one → 11pm crawler read 1,204 posts about the coin, Jev said real people, no farm → crawler walked 6,389 holders, Jev said dev wallet clean, tradable → 12:05am it dumped to $670K, crawler flagged it, Jev said buy, bots bought → 1:30am $2.81M, Jev said out, +$4,710 → 2:35am bought again at $1.97M, 3:45am out at $3.54M, +$1,610 not every call worked, a push at 4:50am faded and cost $285 holding the coin from 11pm made you 29% my bots made 145% on that chart, five green, one red i woke up at 7am to $12,161.37 $100 → $2,197.67 → $4,962.34 → $12,161.37 at second 3 the spider taps the $670K bottom i wrote up the whole chain, crawler to Jev to bots, it's below ↓ costs nothing bookmark this and check me tomorrow show this to the one friend whose crawler only scrapes headlines night 4 is tonight, does the crawler make Jev better or is $12,161 the top?

savip.

3,135,774 views • 5 days ago