Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I gave Space Bunny an ASCII wireframe and told it to compile it into a working dashboard. the ascii map was the entire spec. exact 250px sidebar, responsive grid, live charts on a 2-second mock telemetry loop. It reproduced the layout pixel-for-pixel and wired up all the state: sidebar...

51,702 görüntüleme • 3 gün önce •via X (Twitter)

17 Yorum

Kalsoom (ghotai ) profil fotoğrafı
Kalsoom (ghotai )3 gün önce

That 250px sidebar + live 2-second loop actually working on shot one is the part that sold me.

Parul Gautam profil fotoğrafı
Parul Gautam3 gün önce

The video of that telemetry dashboard looks insane — first-try pixel-perfect from ASCII is actually wild.

Z-Coder profil fotoğrafı
Z-Coder3 gün önce

That telemetry dashboard is seriously impressive getting a pixel-perfect result from ASCII on the first attempt is kind of crazy.

Farhan Azad Shuvra profil fotoğrafı
Farhan Azad Shuvra3 gün önce

Sounds Good!

Patrick's AIBuzzNews profil fotoğrafı
Patrick's AIBuzzNews3 gün önce

Been testing it since yesterday and the speed is the part nobody’s talking about enough.

Arfa Farheen profil fotoğrafı
Arfa Farheen3 gün önce

Dashboard looks production-ready, not “AI slop with extra steps.”

Mushfiq Sajib profil fotoğrafı
Mushfiq Sajib3 gün önce

This is the kind of demo that makes you open OpenCode immediately.

Amira Zairi profil fotoğrafı
Amira Zairi3 gün önce

Anonymous model + 1M context + this kind of frontend output is a dangerous combo

Javeriya Ahsan profil fotoğrafı
Javeriya Ahsan3 gün önce

The ASCII-as-blueprint part is wild. If it really holds pixel-level layout + state wiring from a simple spec, that’s a pretty different way of building UIs.

Nargis Mita profil fotoğrafı
Nargis Mita3 gün önce

Turning ASCII into pixel-perfect UI is impressive.

RAVI KUMAR SAHU profil fotoğrafı
RAVI KUMAR SAHU3 gün önce

Treating ASCII as a precise UI blueprint is seriously impressive.

Dhaval Makwana profil fotoğrafı
Dhaval Makwana3 gün önce

The fact that it wired up nav, dropdown, and filters without extra prompting is what most agents still fail at.

Aaliya profil fotoğrafı
Aaliya3 gün önce

This one actually makes me want to build something tonight instead of just watching the video.

Utkarsh Sharma profil fotoğrafı
Utkarsh Sharma3 gün önce

Who’s actually behind Space Bunny at this point? MiniMax rumors keep getting louder.

Samuel Hu profil fotoğrafı
Samuel Hu3 gün önce

pixel-perfect layout is a good demo. i'd mutate the ascii spec after the first pass and see if the agent updates state without clobbering the live chart. the 2-second loop is where race bugs show up. did you run a second edit?

Muhammad Ayan profil fotoğrafı
Muhammad Ayan3 gün önce

Nobody had ASCII sketches on their 2026 bingo card, But if it's pixel-exact, wireframing just got way cheaper :)

Muhammad Ali profil fotoğrafı
Muhammad Ali3 gün önce

Most models still guess the layout even when you describe it twice. This one treating the wireframe like a blueprint is the difference.

Benzer Videolar

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,764 görüntüleme • 3 ay önce

been playing with whop's new blueprints feature and a part of it changes the whole math on starting a business.. a blueprint is a full business ready to run. not a template you fill in. the actual site, the checkout, tracking, the whop pixel, analytics, all of it live from the first second. you pick a bluepint, name it and deploy, that's it. you're on a .whop.app url taking real payments with nothing left to wire up. i deployed one in the time it takes to read this and these aren't thin little landing pages. multi-page sites, customer accounts, carts, booking, subscriptions, reviews, checkout. full commercial sites out of the box, hosted on Whop for free. the analytics sit in the same dashboard. traffic, conversions, revenue, MRR, churn, ad spend, all in one place,you deploy and you can already see everything. but here's the part that actually that got me invested into it. instead of just building and deploying blueprints, it has other features in-built which can make the whole process easier and every business that gets onboarded through a blueprint you built earns you 10% of whop's gross profit from that business. recurring, per business, for as long as they run. so building a blueprint is its own business. you build one for a niche, put it out there, and every business that runs on it keeps paying you while you do nothing. i spent years thinking distribution was the hard part. build a good blueprint and the distribution is the business.

Sulfur

42,267 görüntüleme • 1 ay önce

Karpathy said something you'll regret ignoring: "We have to keep the AI on the leash. I'm still the bottleneck. I have to make sure this thing isn't introducing bugs and that there's no security issues." He said it at YC talk last year, when the worry was reliability. The models hallucinated and made mistakes no human would, so the leash implied keeping yourself in the loop and checking the output before trusting it. The models are far better now, and the line still holds, for a reason he was not focused on back then. Even a model that writes flawless code today still has no idea who is allowed to run it. Correctness and authorization are different problems, and only correctness improves as the model improves. A perfect agent still hands a tool where anyone can do anything, because permission was never part of the task. I actually tested this in practice with Claude Code. I asked it to build a small internal tool with a button that issues account credits. It worked first try, and running it locally, the credit applied the instant I clicked. Nothing decided who was allowed to click it. The agent wrote the right logic and displayed a success notification. It never checked whether the caller had the right, whether it should pause for a human, or whether anything was logged. And this is not a bug a smarter model can outgrow because the leash was never in the code. Identity, permissions, and audit live in the system that runs the app, not in what the agent generates. To solve this, I took the exact same bundle and hosted it on Retool. The credit write that fired silently on my laptop now stopped at an approval gate, resolved to a real identity through SSO, and landed in an audit log. I wrote none of it. The app inherited the entire boundary the moment it was deployed, and the video shows the before and after. You can try it yourself here: I also wrote a detailed breakdown of the whole thing in my recent article, and I worked with the team to put this together. It walks through the build, the exact moment the credit write went through on my laptop with nobody checking, and then what changed when the same app ran on Retool. It also covers why this is a property of the runtime and not something a better model fixes, which is why devs typically miss this. The article is quoted below.

Akshay 🚀

42,911 görüntüleme • 3 ay önce

CLAUDE BUILT A TRADING SYSTEM ON MY MAC I gave Claude full control over my Mac and just left it running overnight No prompts, no detailed instructions – I just told it to figure out how to make money on Polymarket Then I closed the laptop and went to sleep In the morning, I opened my Mac and saw the terminal still running with logs constantly updating At first it looked like random activity, but once I scrolled through it, I realized it had actually built a structured system overnight It was already tracking wallets Ranking them by performance Filtering out the ones with random entries And focusing only on the ones with consistent behavior What surprised me the most is that it didn’t stop at analysis It organized everything into a working dashboard inside the terminal Capital, PnL, winrate – all updating in real time It even ranked wallets based on performance metrics like ROI, consistency, and execution timing This is the part I would normally spend hours building manually At that point, it was ready to trade, but not actually executing anything yet So I connected it to a Telegram copytrading bot to actually execute the trades, and just let it run Bot: Polymarket: After that, it started opening positions on its own A few hours later I checked the dashboard again Capital: $12,380 P&L: +$23,128 Winrate: 100% 48 trades executed Now I’m not even trading myself I just check the dashboard and see what it’s doing And the strange part is – it keeps getting better the longer it runs

𝗖𝗛𝗔𝗜𝗡 𝗠𝗜𝗡𝗗 ⛓🧠

83,254 görüntüleme • 6 ay önce