Loading video...

Video Failed to Load

Go Home

🧵 1/7 I gave a Flash model a written spec for a 3D physics game. It broke the task into steps, wrote the code, used the tools, ran the project, and eventually produced a billiards game I could actually play. Ant Ling Ling-3.0-flash has 124B total parameters, but activates...

Lonely__MH's profile picture

Lonely

19,677 subscribers

113,220 views • 3 days ago •via X (Twitter)

Science & TechnologyEducationGaming
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Most AI research demos show you a polished answer. This one showed me the disagreement that happened before the answer. I gave Ling-3.0-flash Ant Ling a deliberately difficult question: Do four-day workweeks actually increase productivity, or do they simply compress the same workload into fewer days? Instead of asking for a quick summary, I asked it to coordinate five specialist roles: a scientist, a data analyst, a cross-validator, an archivist, and a research writer. Each role had a separate responsibility. The scientist defined the competing hypotheses. The analyst extracted comparable findings. The archivist tracked the sources. The writer could only use approved claims. And the cross-validator had one job: challenge anything that sounded more confident than the evidence allowed. That last role changed the result. The team reviewed 12 sources and challenged six major claims. Three claims were narrowed. One was rejected entirely. Even a widely repeated claim about a 40% productivity increase did not survive the evidence check. That is the part I wanted to see from an AI research workflow. Not just more information, but visible resistance to weak evidence. The final output included: - a direct executive answer - a structured research paper - a source and evidence table - a disagreement log - a six-slide executive deck - a quality-control summary The conclusion was also more useful than a simple yes or no: reduced working hours may maintain productivity and improve wellbeing under certain conditions, while compressing the same workload into fewer days can increase fatigue and intensity. The evidence did not support a universal productivity claim. What impressed me was not that Ling-3.0-flash generated a long response. Plenty of models can do that. It was the way the model maintained multiple roles, evidence standards, objections, citations, and deliverables across one extended workflow, while preserving uncertainty instead of smoothing it away. That makes Ling-3.0-flash especially interesting for work where execution matters as much as reasoning: research, search, coding, document processing, tool use, repeated checks, and other multi-step agent workflows. The strongest AI systems will not use the largest model for every task. They will combine deep planning with fast, cost-efficient execution. Ling-3.0-flash is built for that execution layer. Ling-3.0-flash is now available on OpenRouter and free to use through August 3, 2026. Try it in your coding, search, research, and tool-use workflows. Then show us what you build. Try Ling-3.0-flash: Documentation:
0:33

Most AI research demos show you a polished answer. This one showed me the disagreement that happened before the answer. I gave Ling-3.0-flash Ant Ling a deliberately difficult question: Do four-day workweeks actually increase productivity, or do they simply compress the same workload into fewer days? Instead of asking for a quick summary, I asked it to coordinate five specialist roles: a scientist, a data analyst, a cross-validator, an archivist, and a research writer. Each role had a separate responsibility. The scientist defined the competing hypotheses. The analyst extracted comparable findings. The archivist tracked the sources. The writer could only use approved claims. And the cross-validator had one job: challenge anything that sounded more confident than the evidence allowed. That last role changed the result. The team reviewed 12 sources and challenged six major claims. Three claims were narrowed. One was rejected entirely. Even a widely repeated claim about a 40% productivity increase did not survive the evidence check. That is the part I wanted to see from an AI research workflow. Not just more information, but visible resistance to weak evidence. The final output included: - a direct executive answer - a structured research paper - a source and evidence table - a disagreement log - a six-slide executive deck - a quality-control summary The conclusion was also more useful than a simple yes or no: reduced working hours may maintain productivity and improve wellbeing under certain conditions, while compressing the same workload into fewer days can increase fatigue and intensity. The evidence did not support a universal productivity claim. What impressed me was not that Ling-3.0-flash generated a long response. Plenty of models can do that. It was the way the model maintained multiple roles, evidence standards, objections, citations, and deliverables across one extended workflow, while preserving uncertainty instead of smoothing it away. That makes Ling-3.0-flash especially interesting for work where execution matters as much as reasoning: research, search, coding, document processing, tool use, repeated checks, and other multi-step agent workflows. The strongest AI systems will not use the largest model for every task. They will combine deep planning with fast, cost-efficient execution. Ling-3.0-flash is built for that execution layer. Ling-3.0-flash is now available on OpenRouter and free to use through August 3, 2026. Try it in your coding, search, research, and tool-use workflows. Then show us what you build. Try Ling-3.0-flash: Documentation:

Rachel🥥

22,963 views • 3 days ago

watch this anon. i gave NVIDIA's biggest model ever a single task. 100 minutes and 440,000 tokens later, it had rendered nothing. not one important thing on the screen. this is Nemotron 3 Ultra. 550 billion parameters, a hybrid Mamba Transformer MoE, the largest model NVIDIA has ever shipped, and they built it specifically for long-running agentic coding. so i handed it exactly that: build a 3D scene from a spec, multiple files, iterate until the tests pass. the same task a frontier model one shotted in minutes. i genuinely wanted to be impressed. it ran for an hour and forty. burned through 440,000 tokens. wrote every file, passed its own tests, and proudly printed "task complete."the browser was blank. the 3D scene never rendered. not once. and the long horizon agentic behavior was genuinely good. it stayed on task the whole hour and forty, wrote real multi-file code, drove its own tools without derailing. it just couldn't turn any of that into something that actually runs. here's the part that gets me. it's a text model, it cannot see its own output. so it sat there looping on a broken vision tool, trying to "look" at the page, hitting error after error, never once reasoning its way out. it declared victory on an empty screen because it had no way to know the screen was empty. to be fair, i genuinely don't know what quant the NIM was serving, so maybe some of that's on the serving, not the model. but the biggest model NVIDIA has ever made, on the exact task it was designed for, couldn't tell it had built nothing in 100 minutes. same task on a local model, below thread👇.
4:07

watch this anon. i gave NVIDIA's biggest model ever a single task. 100 minutes and 440,000 tokens later, it had rendered nothing. not one important thing on the screen. this is Nemotron 3 Ultra. 550 billion parameters, a hybrid Mamba Transformer MoE, the largest model NVIDIA has ever shipped, and they built it specifically for long-running agentic coding. so i handed it exactly that: build a 3D scene from a spec, multiple files, iterate until the tests pass. the same task a frontier model one shotted in minutes. i genuinely wanted to be impressed. it ran for an hour and forty. burned through 440,000 tokens. wrote every file, passed its own tests, and proudly printed "task complete."the browser was blank. the 3D scene never rendered. not once. and the long horizon agentic behavior was genuinely good. it stayed on task the whole hour and forty, wrote real multi-file code, drove its own tools without derailing. it just couldn't turn any of that into something that actually runs. here's the part that gets me. it's a text model, it cannot see its own output. so it sat there looping on a broken vision tool, trying to "look" at the page, hitting error after error, never once reasoning its way out. it declared victory on an empty screen because it had no way to know the screen was empty. to be fair, i genuinely don't know what quant the NIM was serving, so maybe some of that's on the serving, not the model. but the biggest model NVIDIA has ever made, on the exact task it was designed for, couldn't tell it had built nothing in 100 minutes. same task on a local model, below thread👇.

Sudo su

32,589 views • 1 month ago

99% of iPhone users don’t know this: Their phone already has a free music production powerhouse hidden inside. It’s one of the treasures left behind from the Steve Jobs era. Millions of people own an iPhone, iPad, or MacBook — but have never truly opened it. I asked an AI Agent to create a completely new piece of music from scratch. The result surprised me. It wasn’t just generating audio. It could be edited. Sounds, channels, tracks — everything was adjustable. But I didn’t ask AI to generate an MP3. Instead, I asked it to create a: structured, editable, and extendable music project. The model had to understand: 🎹 Main melody 🎻 Harmony relationships 🥁 Rhythm design 🎸 Instrument arrangement 🎼 Multi-track structure The final output was MIDI, which was imported directly into GarageBand. And this reveals a key difference: Traditional AI music tools like SUNO often generate the final audio directly. You get an MP3. It sounds good, but it’s difficult to modify. MIDI is like the Python of the music world. And this is exactly where Ling-3.0-flash Ant Ling shines. It works like a high-speed execution engine in an AI workflow: ⚡ Low latency 💰 Cost-efficient 🔧 Stable tool calling It can transform complex plans into real outputs quickly. In this music creation workflow, it can independently handle: •Which instruments should play •Which notes should be combined •How rhythms should evolve •How different tracks should interact After importing into GarageBand, you can: ✅ Edit the melody ✅ Replace instruments ✅ Adjust tempo ✅ Re-arrange the composition ✅ Add your own creativity I was genuinely impressed by the result. Try it.
0:21

99% of iPhone users don’t know this: Their phone already has a free music production powerhouse hidden inside. It’s one of the treasures left behind from the Steve Jobs era. Millions of people own an iPhone, iPad, or MacBook — but have never truly opened it. I asked an AI Agent to create a completely new piece of music from scratch. The result surprised me. It wasn’t just generating audio. It could be edited. Sounds, channels, tracks — everything was adjustable. But I didn’t ask AI to generate an MP3. Instead, I asked it to create a: structured, editable, and extendable music project. The model had to understand: 🎹 Main melody 🎻 Harmony relationships 🥁 Rhythm design 🎸 Instrument arrangement 🎼 Multi-track structure The final output was MIDI, which was imported directly into GarageBand. And this reveals a key difference: Traditional AI music tools like SUNO often generate the final audio directly. You get an MP3. It sounds good, but it’s difficult to modify. MIDI is like the Python of the music world. And this is exactly where Ling-3.0-flash Ant Ling shines. It works like a high-speed execution engine in an AI workflow: ⚡ Low latency 💰 Cost-efficient 🔧 Stable tool calling It can transform complex plans into real outputs quickly. In this music creation workflow, it can independently handle: •Which instruments should play •Which notes should be combined •How rhythms should evolve •How different tracks should interact After importing into GarageBand, you can: ✅ Edit the melody ✅ Replace instruments ✅ Adjust tempo ✅ Re-arrange the composition ✅ Add your own creativity I was genuinely impressed by the result. Try it.

实践哥MinLi

106,619 views • 1 day ago

✨ Made a new mini feature on Photo AI: [ Grab from 3d model ] So the problem is we're at that stage in time (typical for AI) where image-to-3d models are not good enough but are fun to play with, but we know they'll be good enough in 1-2 years With [ Make 3d model ] you already can turn any Photo AI pic into a 3d model but it still looks hyper clunky and deformed, but it works! One cool idea I had to make that more useful and made now: Let people make a 3d model then change the view of the it with the 3d viewer, then press [ o ] and it grabs a frame of the 3d That image you can then [ Remix ] (img2img), and it becomes a real photo again and that in turn you can then turn into a video again with [ Make video ] So that essentially gives you a fully freeform camera position control to take photos with One thing I need to fix is the background/skybox, I kinda need to take the original photo and remove the person and just get the background for the 3d model viewer, in this case it should be white, but it's a start!
0:51

✨ Made a new mini feature on Photo AI: [ Grab from 3d model ] So the problem is we're at that stage in time (typical for AI) where image-to-3d models are not good enough but are fun to play with, but we know they'll be good enough in 1-2 years With [ Make 3d model ] you already can turn any Photo AI pic into a 3d model but it still looks hyper clunky and deformed, but it works! One cool idea I had to make that more useful and made now: Let people make a 3d model then change the view of the it with the 3d viewer, then press [ o ] and it grabs a frame of the 3d That image you can then [ Remix ] (img2img), and it becomes a real photo again and that in turn you can then turn into a video again with [ Make video ] So that essentially gives you a fully freeform camera position control to take photos with One thing I need to fix is the background/skybox, I kinda need to take the original photo and remove the person and just get the background for the 3d model viewer, in this case it should be white, but it's a start!

@levelsio

119,210 views • 1 year ago

I plugged MiniMax (official) M3 into Claude Code in under 5 minutes and gave it a real task. most models need hand-holding every few steps. M3 ran 147 iterations on its own. what it actually did: → took a broken CUDA kernel → ran it for 24 hours, autonomously → pushed hardware efficiency from 7.6% to 71.3% → shipped a 9.4x speedup I didn't touch it once across that whole window. the rest of the spec sheet: → 1M token context window → native multimodal from day one → fully open weights pricing: → $20/month for 1.7B tokens → $50/month for 5.1B tokens → text, image, speech, and music all share one pool usually with this kind of capability the bill catches up fast. M3 keeps both lines low at the same time. that's the part that surprised me. and if this is what M3 does at launch, the full rollout is going to be one to watch. what would you build with 1M context? #MiniMax #MiniMaxM3 #ClaudeCode #LLM
0:25

I plugged MiniMax (official) M3 into Claude Code in under 5 minutes and gave it a real task. most models need hand-holding every few steps. M3 ran 147 iterations on its own. what it actually did: → took a broken CUDA kernel → ran it for 24 hours, autonomously → pushed hardware efficiency from 7.6% to 71.3% → shipped a 9.4x speedup I didn't touch it once across that whole window. the rest of the spec sheet: → 1M token context window → native multimodal from day one → fully open weights pricing: → $20/month for 1.7B tokens → $50/month for 5.1B tokens → text, image, speech, and music all share one pool usually with this kind of capability the bill catches up fast. M3 keeps both lines low at the same time. that's the part that surprised me. and if this is what M3 does at launch, the full rollout is going to be one to watch. what would you build with 1M context? #MiniMax #MiniMaxM3 #ClaudeCode #LLM

Nelly;

17,576 views • 1 month ago

I’ve never shared this before. But I wanted to share a small story about the biggest project I had taken once. The project was one of the largest we’ve ever worked on. A product built from scratch, valued close to a billion dollars. The whole team didn’t just work on it; we lived it. The energy, the pressure, the excitement… it was unlike anything we had experienced before. We were fully booked for the next 6 months on this one project. Enjoyed every moment of it though, through and through.
1:23

I’ve never shared this before. But I wanted to share a small story about the biggest project I had taken once. The project was one of the largest we’ve ever worked on. A product built from scratch, valued close to a billion dollars. The whole team didn’t just work on it; we lived it. The energy, the pressure, the excitement… it was unlike anything we had experienced before. We were fully booked for the next 6 months on this one project. Enjoyed every moment of it though, through and through.

Arafat

47,009 views • 7 months ago

After ClawdBot, the next big thing could be Qoder Quest. Most of the coding tools today need multiple iterations of testing, debugging, and prompts. An autonomous coding tool would be game changer. Qoder Quest is exactly this. It’s designed to take ownership of your projects. For sure, it is not a replacement for your mental model. Instead of line-by-line hand-holding, the workflow looks like this: – Describe a goal: tell it what you want to build – Approve the Spec: approve the technical spec first to align Quest with your mental model – Walk away: let the Quest run autonomously Attached is a video of me playing around with Quest for the first time. Get started with it: New users could have a 2-week pro trial with some credits to execute 5 Quest tasks. Appreciate the Qoder team for collaborating with me on this deep dive.
5:58

After ClawdBot, the next big thing could be Qoder Quest. Most of the coding tools today need multiple iterations of testing, debugging, and prompts. An autonomous coding tool would be game changer. Qoder Quest is exactly this. It’s designed to take ownership of your projects. For sure, it is not a replacement for your mental model. Instead of line-by-line hand-holding, the workflow looks like this: – Describe a goal: tell it what you want to build – Approve the Spec: approve the technical spec first to align Quest with your mental model – Walk away: let the Quest run autonomously Attached is a video of me playing around with Quest for the first time. Get started with it: New users could have a 2-week pro trial with some credits to execute 5 Quest tasks. Appreciate the Qoder team for collaborating with me on this deep dive.

Pratham

104,021 views • 5 months ago

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.
4:15

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,574 views • 1 month ago

Task Master CLI will makes Cursor 10x better at building projects. I created a full video demo of how it works. For those that don't want to watch. Here's what happens: 1️⃣ Install npm i task-master-ai CLI 2️⃣ Give it a description of your project. It will generate a PRD 3️⃣ It will then convert the PRD into tasks (10 detailed .txt files and a .json that acts as a local db to task track status) 4️⃣ Ask it to do a task. It will do the task and mark it off as done. Each task can also be broken down into small tasks using "expand" command. Following these steps it will build out an entire project. This is the future of dev and how tools like Manus work. But you can run it locally and follow step by step to make sure you're happy with what's happening. Seems a fitting to be posting about Task Master the day before Passover starts. Good job by Eyal Toledano who built this project.
12:18

Task Master CLI will makes Cursor 10x better at building projects. I created a full video demo of how it works. For those that don't want to watch. Here's what happens: 1️⃣ Install npm i task-master-ai CLI 2️⃣ Give it a description of your project. It will generate a PRD 3️⃣ It will then convert the PRD into tasks (10 detailed .txt files and a .json that acts as a local db to task track status) 4️⃣ Ask it to do a task. It will do the task and mark it off as done. Each task can also be broken down into small tasks using "expand" command. Following these steps it will build out an entire project. This is the future of dev and how tools like Manus work. But you can run it locally and follow step by step to make sure you're happy with what's happening. Seems a fitting to be posting about Task Master the day before Passover starts. Good job by Eyal Toledano who built this project.

Elie Steinbock

36,636 views • 1 year ago

This is a pretty wild model! You can use it to turn an image into a 3D object with texture. The quality is out of this world! I'm not even a designer, and I've been using this nonstop for the last 2 hours. The model is Hunyuan 3D 2.1. It's open source. You'll find model weights, training/inference code, data pipelines, and architecture on their repository. You can even fine-tune it if you want! GitHub Repository: By the way, the model runs on consumer-grade GPUs. You don't need a datacenter for this! I've been using the model from the HuggingFace demo page: To use it, go to the link and upload an image. That's it! Check out the video I recorded for a couple of examples.
2:42

This is a pretty wild model! You can use it to turn an image into a 3D object with texture. The quality is out of this world! I'm not even a designer, and I've been using this nonstop for the last 2 hours. The model is Hunyuan 3D 2.1. It's open source. You'll find model weights, training/inference code, data pipelines, and architecture on their repository. You can even fine-tune it if you want! GitHub Repository: By the way, the model runs on consumer-grade GPUs. You don't need a datacenter for this! I've been using the model from the HuggingFace demo page: To use it, go to the link and upload an image. That's it! Check out the video I recorded for a couple of examples.

Santiago

44,783 views • 1 year ago

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

118,124 views • 1 month ago

AN OPENCLAW AI AGENT JUST DESIGNED A 3D CHARACTER IN BLENDER AND SENT IT TO A 3D PRINTER. SHE DIDN'T TOUCH A SINGLE BUTTON. This is what running an OpenClaw AI agent on a Mac Mini actually looks like. She described what she wanted. The agent did everything else. Blender opened automatically. Character designed. Put in space. Animated with blinking eyes and stomping feet. Landing page built and live. Model sliced. File sent to 3D printer. Printer started moving. All from conversation. Zero code. Zero design skills. Zero manual work. Here's why this matters beyond the demo: Custom 3D printed figures sell for $30-$200 each on Etsy and at conventions. The people making serious money aren't artists. They're the ones who can produce custom designs fast. An AI agent that goes from description to printed figure autonomously is a business model not a toy. "I was just talking to the guy and he made it happen." Bookmark this. Full demo in the video below.
1:29

AN OPENCLAW AI AGENT JUST DESIGNED A 3D CHARACTER IN BLENDER AND SENT IT TO A 3D PRINTER. SHE DIDN'T TOUCH A SINGLE BUTTON. This is what running an OpenClaw AI agent on a Mac Mini actually looks like. She described what she wanted. The agent did everything else. Blender opened automatically. Character designed. Put in space. Animated with blinking eyes and stomping feet. Landing page built and live. Model sliced. File sent to 3D printer. Printer started moving. All from conversation. Zero code. Zero design skills. Zero manual work. Here's why this matters beyond the demo: Custom 3D printed figures sell for $30-$200 each on Etsy and at conventions. The people making serious money aren't artists. They're the ones who can produce custom designs fast. An AI agent that goes from description to printed figure autonomously is a business model not a toy. "I was just talking to the guy and he made it happen." Bookmark this. Full demo in the video below.

SCOTTY BEAM

17,209 views • 1 month ago

🧵1/3 I partnered with Kling to make a promo for their new 3.0 model. I came up with the concept, created it and delivered it all on my own in 3 days of early access, I wanted to make something that showed how Kling could be used to tell a diverse range of stories in a diverse range of styles. I've honestly been blown away be how incredible the model is and I haven't even scratched the surface of features like the new 3.0 OMNI model. For me Kling 2.6 was already best in class for most things but 3.0 sees massive improvements to video quality and detail (no need to add grain to mask imperfections) and prompt adherence. Also you can time your generations to be as long as 15 seconds and as short as 3, this is fantastic for pacing your scenes. Read on to find out more about the new Performance and Multi shot features!👇
1:26

🧵1/3 I partnered with Kling to make a promo for their new 3.0 model. I came up with the concept, created it and delivered it all on my own in 3 days of early access, I wanted to make something that showed how Kling could be used to tell a diverse range of stories in a diverse range of styles. I've honestly been blown away be how incredible the model is and I haven't even scratched the surface of features like the new 3.0 OMNI model. For me Kling 2.6 was already best in class for most things but 3.0 sees massive improvements to video quality and detail (no need to add grain to mask imperfections) and prompt adherence. Also you can time your generations to be as long as 15 seconds and as short as 3, this is fantastic for pacing your scenes. Read on to find out more about the new Performance and Multi shot features!👇

Uncanny Harry AI

29,181 views • 5 months ago

Claude Opus 5 just one-shotted this FPS. Less than 1 hour from prompt to playable demo. Every weapon, enemy, mechanic and environment was generated from scratch. Prompt below 👇 There is no prompt below, because the first section is exactly the kind of post I’m tired of seeing every time a new model drops. A flashy demo, “one-shot” in the caption, “built in under an hour”… anything to farm impressions while conveniently hiding the actual process. If it was really made from a single prompt, show the prompt. That’s what I do on this account. When I claim something is a one-prompt prototype built with GPT-5.6 Sol Ultra and Codex, I share the prompt publicly so anyone can verify it. AI is already making game prototyping incredible. We don’t need fake “one-shot” stories to prove it. Original footage:
0:36

Claude Opus 5 just one-shotted this FPS. Less than 1 hour from prompt to playable demo. Every weapon, enemy, mechanic and environment was generated from scratch. Prompt below 👇 There is no prompt below, because the first section is exactly the kind of post I’m tired of seeing every time a new model drops. A flashy demo, “one-shot” in the caption, “built in under an hour”… anything to farm impressions while conveniently hiding the actual process. If it was really made from a single prompt, show the prompt. That’s what I do on this account. When I claim something is a one-prompt prototype built with GPT-5.6 Sol Ultra and Codex, I share the prompt publicly so anyone can verify it. AI is already making game prototyping incredible. We don’t need fake “one-shot” stories to prove it. Original footage:

Givros

14,794 views • 3 days ago

I just ran a full research project without doing any research. Lemma by Analemma did everything: 1. Explore I typed a question. It mapped the entire field. Concepts, references, key papers. Done. 2. Survey I asked for a literature review. It gave me 50+ pages with real citations. Not a summary. A publication-grade draft. 3. Code I described an experiment. It wrote the code, ran it, showed results. 4. FARS I gave it a research direction. It generated hypotheses, planned experiments, ran them, and wrote the full paper. Zero input from me after that. This is the first tool I've used that actually runs research instead of just helping you do it. FARS already ran live and produced 100 papers in 10 days. One every 2 hours. Watch it here: This is what "Vibe Research" looks like.
0:30

I just ran a full research project without doing any research. Lemma by Analemma did everything: 1. Explore I typed a question. It mapped the entire field. Concepts, references, key papers. Done. 2. Survey I asked for a literature review. It gave me 50+ pages with real citations. Not a summary. A publication-grade draft. 3. Code I described an experiment. It wrote the code, ran it, showed results. 4. FARS I gave it a research direction. It generated hypotheses, planned experiments, ran them, and wrote the full paper. Zero input from me after that. This is the first tool I've used that actually runs research instead of just helping you do it. FARS already ran live and produced 100 papers in 10 days. One every 2 hours. Watch it here: This is what "Vibe Research" looks like.

Muhammad Ayan

39,960 views • 1 month ago

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.
0:35

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.

Arlan

28,405 views • 8 months ago

Gemini 3.1 Flash-Lite is the model to build always on multimodal AI Agents. I just built a memory agent with Google ADK that runs 24/7. Feed it text, images, audio, video or PDFs. It reads, connects and consolidates everything while you sleep. 100% Opensource code.
1:05

Gemini 3.1 Flash-Lite is the model to build always on multimodal AI Agents. I just built a memory agent with Google ADK that runs 24/7. Feed it text, images, audio, video or PDFs. It reads, connects and consolidates everything while you sleep. 100% Opensource code.

Shubham Saboo

24,930 views • 4 months ago

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):
19:42

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):

Alex Finn

40,955 views • 10 months ago

UPDATE: Charlie Kirk 🚨 Muzzle Flash: Second Shooter Location, Reflection, or Both? This video captures a flash on a window right as Charlie Kirk was shot. Let’s break this down… follow the numbers on the videos. #1. This video shows what appears to be a muzzle flash, just as Charlie is shot, leading people to believe the shooter was to Charlie’s right.. Notate the people to the left of the flash #2. This photo shows the location of the flash. Notate people to the left, on a middle-landing on a staircase. #3. This photo shows a clearer image showing both the middle-landing and the same location of the flash. It is a window. #4 . This video shows the building behind Charlie, which is a long hallway. This debunks any claims the shot came from here. — I zoom in where Charlie was — I zoom in on staircase — I zoom in on the window/flash — I zoom in on where suspected shooter was #5. I notate the flash reflection angles. — Video angle #1 notated — two reflection paths notated in relation to Video angle #1. 1. Reflection angle shows where we were told the shooter was. 2. Reflection angle shows mirrored angle, obviously where there is no reports of a shooter being in. 🔻 Final conclusion: This to me is very likely a muzzle flash reflection from a far off location. I am unsure of the reflection angle however, but this can be 100% proven if someone were to recreate the angles… maybe with a flash camera. If anyone is willing to, or has the means to do this (safely), this will either prove the shot came where the FBI said it came from, or it will prove there was a second shooter, in the direction of the mirrored angle.
0:16

UPDATE: Charlie Kirk 🚨 Muzzle Flash: Second Shooter Location, Reflection, or Both? This video captures a flash on a window right as Charlie Kirk was shot. Let’s break this down… follow the numbers on the videos. #1. This video shows what appears to be a muzzle flash, just as Charlie is shot, leading people to believe the shooter was to Charlie’s right.. Notate the people to the left of the flash #2. This photo shows the location of the flash. Notate people to the left, on a middle-landing on a staircase. #3. This photo shows a clearer image showing both the middle-landing and the same location of the flash. It is a window. #4 . This video shows the building behind Charlie, which is a long hallway. This debunks any claims the shot came from here. — I zoom in where Charlie was — I zoom in on staircase — I zoom in on the window/flash — I zoom in on where suspected shooter was #5. I notate the flash reflection angles. — Video angle #1 notated — two reflection paths notated in relation to Video angle #1. 1. Reflection angle shows where we were told the shooter was. 2. Reflection angle shows mirrored angle, obviously where there is no reports of a shooter being in. 🔻 Final conclusion: This to me is very likely a muzzle flash reflection from a far off location. I am unsure of the reflection angle however, but this can be 100% proven if someone were to recreate the angles… maybe with a flash camera. If anyone is willing to, or has the means to do this (safely), this will either prove the shot came where the FBI said it came from, or it will prove there was a second shooter, in the direction of the mirrored angle.

MJTruthUltra

10,665,164 views • 10 months ago