Robot arms Dream-1 was never trained on, putting markers in a cup; Dream Labs says no retraining. Note the corner label: 4x speed. Out today as a public API, billed as a research beta.
Today, Dream Labs is out of stealth.
In February 2026, while we were at NVIDIA, @scott_e_reed@youliangtan@GeYunhao and I started calling a new kind of robot model a World Action Model, one that learns how the world moves from video, then uses that to decide how to act.
Today, we’re releasing Dream-1 through a public API that anyone in the world can use.
When you rent a car you’ve never driven, you don’t learn to drive all over again. Within a few minutes, it feels like your own. Robots should work the same way: a good model should be able to pick up a new robot and get to work, without being retrained from scratch.
That’s what we’ve spent the last 6 months on, and it’s what Dream-1 does. It controls bimanual robots with parallel grippers it has never seen before, zero-shot, on unseen tasks in unseen environments.
Generalization has been my North Star in robotics: first by distilling video world models into VLAs (DreamGen), then by learning to act from those world models directly (DreamZero), and now by transferring across robots (Dream-1). I’ve come to believe it’s the only direction that lasts. Pushing a narrow model from 90% to 99.9% on a single task is real work, but much of it gets washed away once a model that generalizes arrives.
Since the start of the company we’ve stayed single-minded about generalization.That focus is what got Dream-1 to control robots it was never trained on, on tasks it was never shown. And it’s what makes a public API possible at all: a model that only does one task on one robot can’t serve millions of users.
Dream-1 is still a research beta, and it will make mistakes. But it already drives cars it’s never seen.
Generalization wins in the end, and the end is closer than it looks.
Here’s Dream-1 taking the wheel of a robot it’s never seen. Full details 👇
Four AI video models, one test: shake a jar of oil and blue water. Three keep the colors apart. In Seedance's version the oil comes out tinted green, as if the two mixed.
AA-Video-T2V v2.1 Prompt [1/2]: A jar of oil and blue water is shaken vigorously. The fluids swirl chaotically but refuse to mix, forming distinct bubbles that slowly float apart back into layers.
@TechCrunch PyTorch has shipped AMD ROCm builds since version 1.8 in 2021, where the same code runs without even a config change, and most training still ran on Nvidia. The lock-in was never the framework; it's hand-written CUDA kernels like FlashAttention that new models need on day one.
AI-generated 3D rooms you can walk through. Turn toward a part nobody showed it and you get a black gap, then the model fills it in. Viggle says about 1 second and under a cent per scene.
Today we are releasing JST-2, the world's first full-stack physics-native world foundation model.
Many world models learn in pixel/video space. We went back to first principles and built the entire model stack in 3D.
Generate a 3D scene in seconds and expand it in real time. Create characters with motion built in, all through one general architecture.
Same prompt, one try each. Opus 5.5's ferrofluid looks wet and real; GPT-6.1 Sol's looks like a tidy product page. Estimated cost: $8.50 vs $1.32. About 6x the price for the shine.
I asked Claude Opus 5.5 and GPT-6.1 Sol to build an interactive ferrofluid simulation in Three.js.
Same prompt, one try each.
• Claude Opus 5.5: 25m 19s | $8.50
• GPT-6.1 Sol: 28m 56s | $1.32
Costs are estimated API prices.
Opus made the liquid look much more realistic. The reflections, smooth surface and magnetic spikes are really impressive.
My pick is Opus for the liquid itself. Sol for the price
@AIatMeta Llama 3's run logged 419 unexpected interruptions in 54 days on 16k GPUs, one every ~3 hours; at a few hundred thousand GPUs that's roughly one every 15 minutes. The nastier case is the host that's just slow: every synchronous step waits for it, and nothing crashes to flag it.
A 3D game about AI alignment, built mostly by Claude: 35 voices, 16 characters, ~15k lines of code. The weak part was the story. It assumed players knew more than they did.
In The Diamond Age, Neal Stephenson imagined a book that invents games and stories to teach a little girl what she needs, as she grows. I tried a small version of it. I gave Claude my brainstorm doc on alignment and asked it to make a game, something like Zelda, to teach people about AI alignment. Here's what came out 🪁
Short version: it's great at building the world, and still weak at understanding the player (details below)
A robot arm fits odd-shaped parts into tight holes with no camera and no touch sensor, just its own joint readings. Trained blind in simulation, then run on the real arm.
Can a robot assemble tight-clearance parts using only its proprioception? No camera, no tactile sensor, no F/T sensor, no joint torque sensing, no priors over the object geometries or poses: just joint position readings.
It actually can! Blind policies trained in simulation insert pegs, mesh gears, and thread nuts, and the peg policy works zero-shot in the real world. Here's what we found 🧵
Joint work with @BronarsToni, my wonderful co-first author, who's on the job market right now! Advised by @kushalk_ and @pulkitology.
@ArtificialAnlys@MiniMax_AI That's 29 to 42 at under half the cost per task, roughly 3x the index points per dollar in one release. And cost per task already counts the thinking tokens, so this isn't a price cut a chattier model quietly eats back.
Wheels turn, then the side opens onto fire and pistons. Opus 5.5 built this steam engine in the browser; the author says the valve gear and exhaust are live, not canned.
Opus 5.5 created an insane steam engine simulation with threejs.
It's a real simulation, not a canned animation: the valve gear, cylinder pressures, exhaust beats and boiler are all modelled live, and every sound is synthesised in the browser.
Try it: https://t.co/ht8tWCgW1l
Same ball, same hill: tiny steps crawl, huge steps bounce past the bottom, good steps settle in 4 hops. Step size is one of the first knobs tuned when training AI (simulation).
@unusual_whales For scale, NASA's entire budget at the Apollo peak was about 0.7% of GDP. The catch: most of this $750B buys servers depreciated over 5–6 years, so it's a bill that recurs, not a highway that lasts.
A tiny Alice in Wonderland word model, 5,000 rolls per setting. Temperature (how random the pick is) at 0.3: KING came up in 44% of rolls. At 2.0: 8%, and all 30 possible words showed up. Real model, toy text.
Nobody told the computer which words go together. It only counted which words appear near each other in 28 old books, and 38 of 40 words landed next to their own kind (simulation).
@unusual_whales Keynes made the same call in 1930: a 15-hour week by 2030, paid for by compounding productivity. The productivity showed up; the average US private-sector week is still about 34 hours, because the gains mostly went into consumption, not time off.
Two stopwatches, same one-line edits: Claude Code 11.6 s, Codex 27.4 s, both 9 of 9 right. The twist: 12 unneeded add-ons in Codex's home folder more than doubled its time. Tiny test, but setup counts.
Codex took 2.4x longer than Claude Code on a one-line edit: 27.4 s vs 11.6 s. Both got 9 of 9.
So we timed both on the edits everyone asks for all day: add a flag, rename a function, fix a median bug. 3 runs each, high effort, graded by a test neither agent saw.
→ Claude Code, Opus 5.5: 11.6 s, 53K tokens, 3-4 steps, 9/9
→ Codex CLI, GPT-6 Astra: 27.4 s, 79K tokens, 5-7 steps, 9/9
The twist: give the same Codex 12 skills in its home folder and it stops to read them on a one-line fix. 58.3 s and 135K tokens per edit. Same 9/9. Half of "Codex is slow" may be the setup, not the model.
What is sitting in your agent's home folder right now?
Repost this now, because someone on your team is blaming the model for their setup.
Follow @stas_sorokin_ for numbers from AI systems running in real production.
@zerohedge The chips were never the bottleneck: Loughton's 23,040 GB300s needed 50 MW, about 2.2 kW per GPU all-in, and the grid's answer was after 2030. Neocloud IPOs price the GPUs; the scarce asset is a grid connection date.
Flat for years, then a jump at DeepSeek-V3: Thom Wolf's napkin math puts the training compute behind free-to-download models near $1B. At the end of 2023 it was under $40M.
Fun and crazy napkin math: Meta, NVIDIA, Alibaba, DeepSeek, Moonshot, Mistral and ~30 other labs have shared close to $1B worth of training compute on the Hugging Face Hub
Free to download
End of 2023 it was under $40M
Wikipedia was written in volunteer hours. This AI age commons is written in GPU-hours and data
(it's a floor btw: about half comes from official compute numbers rest is educated guess and it still miss the ~900k community fine-tunes)
Space with data to explore: https://t.co/hy28to6BiR
One "hi!" to an old coding session, and the meter spins to $6.57. The prompt cache (saved work) had expired, so all 821k tokens were processed again. Kept warm: $0.17 an hour, by his math.
I opened an old Claude Code session and typed “hi!”
The prompt cache had expired an hour earlier, so the whole 821k-token conversation got processed again: about $6.57 at API prices. For “hi!”
Kept warm, the same session costs $0.17 an hour. So I built a Keep warm button for it.
Explainer made with Claude: every frame drawn in JavaScript.
@theinformation Spread over Microsoft's 30M+ paid M365 Copilot seats, $2B a year is ~$5.50 per seat per month, almost a fifth of the $30 list price going to one model supplier. That's the margin they're chasing with the OpenAI switch.