Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

50% cheaper Claude inference with just one line of code change! - Remove → model="claude-opus-4-8" - Add → model="ship-like/claude-opus-4-8" I verified the cost saving in my own terminal by invoking the same Anthropic model with the same prompt. The underlying engineering by Ship is actually interesting, and the patterns...

akshay_pachaar's profile picture

Akshay 🚀

282,646 subscribers

63,438 Aufrufe • vor 6 Tagen •via X (Twitter)

Wissenschaft & TechnologieBildungNachrichten & Politik
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

PAYING PER MODEL IS THE DUMBEST THING IN TECH RIGHT NOW i was paying 3x what i needed to for AI inference the grid lets you buy a quality spec instead of a specific model.. it routes every request in real time to the cheapest option that qualifies swap one url and your code keeps working exactly the same openai-compatible, one line to switch, 200M free tokens to start
0:19

PAYING PER MODEL IS THE DUMBEST THING IN TECH RIGHT NOW i was paying 3x what i needed to for AI inference the grid lets you buy a quality spec instead of a specific model.. it routes every request in real time to the cheapest option that qualifies swap one url and your code keeps working exactly the same openai-compatible, one line to switch, 200M free tokens to start

Robin Delta

15,729 Aufrufe • vor 2 Monaten

Don't train the model, evolve the harness. I read a brilliant blog post from Hugging Face where they took a frozen open model scoring 0% on a hard legal agent benchmark, left its weights alone, and let an automated loop rewrite only the code around it. That code layer is the harness, the runtime wrapper that feeds the model context, runs its tool calls, and decides when a run ends. By the time the loop finished, the system had essentially matched Sonnet 4.6 on the benchmark's headline metric, at roughly 7x lower cost per task. Zero weights changed. The gain existed because of where the model was failing. The judge only grades files saved in the right place under the exact requested filename, and the model kept doing the legal analysis correctly, then saving it under the wrong name, dropping it in a scratch folder, or never writing it at all. So the 0% was never measuring legal reasoning. It was measuring the harness. Hand-tuning that layer is slow and model-specific, so they automated it. A Claude proposer adds exactly one mechanism per iteration, and an outer loop keeps it only if it clearly beats the current best, so accepted mechanisms compound. What the loop discovered says a lot about where agents actually fail. → The biggest single gain was file handling, not intelligence. An automatic step that lands the deliverable exactly where the judge expects it beat every prompt change, with zero extra model tokens. → Code fixes transferred across models, prompt playbooks did not. The same harness lifted a smaller model from the same family by 14 points, but the tuned prompts hurt a different model family on tasks it could already finish. → The harness mattered more than anything else. Same model, same judge, same tasks, and five different harnesses scored anywhere between 3.5% and 80.1%. The gains do eventually flatten, and the remaining misses look like real capability gaps. At some point the wrapper runs out of tricks and the model has to carry the work. But the lesson holds. A benchmark score measures the model and its harness together, and until the harness is fixed, it's impossible to know which one failed. I highly recommend reading this: I also wrote a deep dive on agent harness engineering a while back, covering the orchestration loop, tools, memory, context management, and everything that turns a stateless LLM into a capable agent. The article is quoted below.
0:18

Don't train the model, evolve the harness. I read a brilliant blog post from Hugging Face where they took a frozen open model scoring 0% on a hard legal agent benchmark, left its weights alone, and let an automated loop rewrite only the code around it. That code layer is the harness, the runtime wrapper that feeds the model context, runs its tool calls, and decides when a run ends. By the time the loop finished, the system had essentially matched Sonnet 4.6 on the benchmark's headline metric, at roughly 7x lower cost per task. Zero weights changed. The gain existed because of where the model was failing. The judge only grades files saved in the right place under the exact requested filename, and the model kept doing the legal analysis correctly, then saving it under the wrong name, dropping it in a scratch folder, or never writing it at all. So the 0% was never measuring legal reasoning. It was measuring the harness. Hand-tuning that layer is slow and model-specific, so they automated it. A Claude proposer adds exactly one mechanism per iteration, and an outer loop keeps it only if it clearly beats the current best, so accepted mechanisms compound. What the loop discovered says a lot about where agents actually fail. → The biggest single gain was file handling, not intelligence. An automatic step that lands the deliverable exactly where the judge expects it beat every prompt change, with zero extra model tokens. → Code fixes transferred across models, prompt playbooks did not. The same harness lifted a smaller model from the same family by 14 points, but the tuned prompts hurt a different model family on tasks it could already finish. → The harness mattered more than anything else. Same model, same judge, same tasks, and five different harnesses scored anywhere between 3.5% and 80.1%. The gains do eventually flatten, and the remaining misses look like real capability gaps. At some point the wrapper runs out of tricks and the model has to carry the work. But the lesson holds. A benchmark score measures the model and its harness together, and until the harness is fixed, it's impossible to know which one failed. I highly recommend reading this: I also wrote a deep dive on agent harness engineering a while back, covering the orchestration loop, tools, memory, context management, and everything that turns a stateless LLM into a capable agent. The article is quoted below.

Akshay 🚀

243,774 Aufrufe • vor 24 Tagen

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:
0:17

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:

Sean Strong

115,693 Aufrufe • vor 10 Monaten

✨ 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 Aufrufe • vor 1 Jahr

let me save you 3 hours of head scratching. if you're running local models like Qwen3.5-35B-A3B through Claude Code via llama.cpp's Anthropic endpoint, the chain will break every 3 to 5 minutes. tool call fails. flow stops. you reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness chokes on local inference latency. switch to OpenCode. same localhost endpoint. same model. same GPU. the chain doesn't break. the tradeoff: OpenCode sometimes loops. the model forgets what it already read and repeats the same tool call. but a loop you can interrupt. a broken chain kills your momentum and you start over. watch both side by side. proprietary agent vs open source agent. same 3B model. different failure modes. pick your poison.
0:19

let me save you 3 hours of head scratching. if you're running local models like Qwen3.5-35B-A3B through Claude Code via llama.cpp's Anthropic endpoint, the chain will break every 3 to 5 minutes. tool call fails. flow stops. you reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness chokes on local inference latency. switch to OpenCode. same localhost endpoint. same model. same GPU. the chain doesn't break. the tradeoff: OpenCode sometimes loops. the model forgets what it already read and repeats the same tool call. but a loop you can interrupt. a broken chain kills your momentum and you start over. watch both side by side. proprietary agent vs open source agent. same 3B model. different failure modes. pick your poison.

Sudo su

72,501 Aufrufe • vor 4 Monaten

i built an open world minigame that's controlled with hand movements only here's a step-by-step tutorial: > started with my mediapipe + threejs template (see QT) > added a 3D model made by quaternius > sent a few prompts to gemini 3... --- prompt #1: repurpose the attached script, but now I want to import a gltf model (assets/model.gltf) and use that in the scene instead of the cube when the user moves their hand, a waypoint indicator should move around the scene, and the 3D model should smoothly move there when the user makes a fist, the model should jump the 3D model contains bundled animations in it. use the "idle", "run", and "jump" animations --- prompt #2: make this a procedural open world adventure. generate very simple procedural voxel terrain when the model gets near the edges of the screen, the camera should move, allowing the model to keep going in that direction --- prompt #3: add some floating glowing gems around the map that the user can collect --- i made some manual tweaks for styling and game feel, but that's the gist of it thanks for reading if you got all the way here full code is available at my link in bio
0:15

i built an open world minigame that's controlled with hand movements only here's a step-by-step tutorial: > started with my mediapipe + threejs template (see QT) > added a 3D model made by quaternius > sent a few prompts to gemini 3... --- prompt #1: repurpose the attached script, but now I want to import a gltf model (assets/model.gltf) and use that in the scene instead of the cube when the user moves their hand, a waypoint indicator should move around the scene, and the 3D model should smoothly move there when the user makes a fist, the model should jump the 3D model contains bundled animations in it. use the "idle", "run", and "jump" animations --- prompt #2: make this a procedural open world adventure. generate very simple procedural voxel terrain when the model gets near the edges of the screen, the camera should move, allowing the model to keep going in that direction --- prompt #3: add some floating glowing gems around the map that the user can collect --- i made some manual tweaks for styling and game feel, but that's the gist of it thanks for reading if you got all the way here full code is available at my link in bio

AA

131,799 Aufrufe • vor 7 Monaten

Added context to my tiny diffusion model to enable sequential generation of longer outputs! Currently the context is a quarter of the sequence length (seq_len=256, context_len=64). I have a theory that the less semantic-value-per-token, the worse the “curse of parallel decoding” is. With parallel decoding, we independently predict multiple tokens in one step. With the sentence “My poker hand was a ___ ___”, two valid predictions are “two pair” and “straight flush”. Because each token prediction is independent though, we can end up with a nonsensical output like “two flush”. This seems to be exacerbated with low semantic-value-per-token, as now you need more tokens to express the same concept. Instead of needing to independently predict two tokens, we might need to predict 10 instead (which is of course much harder). The model currently has noticeably worse output compared to nanogpt (similar size) and I believe this is a main reason. I’ll try adding confidence-aware parallel decoding (from NVIDIA’s Fast-dLLM paper) and other tricks and see how much they improve generation quality.
0:12

Added context to my tiny diffusion model to enable sequential generation of longer outputs! Currently the context is a quarter of the sequence length (seq_len=256, context_len=64). I have a theory that the less semantic-value-per-token, the worse the “curse of parallel decoding” is. With parallel decoding, we independently predict multiple tokens in one step. With the sentence “My poker hand was a ___ ___”, two valid predictions are “two pair” and “straight flush”. Because each token prediction is independent though, we can end up with a nonsensical output like “two flush”. This seems to be exacerbated with low semantic-value-per-token, as now you need more tokens to express the same concept. Instead of needing to independently predict two tokens, we might need to predict 10 instead (which is of course much harder). The model currently has noticeably worse output compared to nanogpt (similar size) and I believe this is a main reason. I’ll try adding confidence-aware parallel decoding (from NVIDIA’s Fast-dLLM paper) and other tricks and see how much they improve generation quality.

Nathan Barry

89,040 Aufrufe • vor 9 Monaten

World Models are the path for some AI Models in the future. But how can we efficiently train these models to not only see the world the way humans do but to see the world in a new and unique way. By visualizing, what is normally sequenced audio patterns, we can derive much more insights. Here we see Paganini in a visual form that can than be described and transcribed into a World Model. We can observe connections in a manner that may not have been clear prior to the digitalization of music and sound in this way. The company with the most valuable potential in building a World Model is Tesla. Not that this type of visualization is being used, but that the mechanisms are in place, and the technology is in place for the company to thrive in this new form of AI.
0:19

World Models are the path for some AI Models in the future. But how can we efficiently train these models to not only see the world the way humans do but to see the world in a new and unique way. By visualizing, what is normally sequenced audio patterns, we can derive much more insights. Here we see Paganini in a visual form that can than be described and transcribed into a World Model. We can observe connections in a manner that may not have been clear prior to the digitalization of music and sound in this way. The company with the most valuable potential in building a World Model is Tesla. Not that this type of visualization is being used, but that the mechanisms are in place, and the technology is in place for the company to thrive in this new form of AI.

Brian Roemmele

57,454 Aufrufe • vor 8 Monaten

Day 12/90 of Inference Engineering What is chunked prefill within vLLM? In continuation of yesterday's post on the high level architecture of vLLM, I want to dive deeper into vLLM core engine starting with the mechanics of chunked prefill. In this post, I will closely follow the original blog on the anatomy of vLLM. To start, let's define chunked prefill. It's a runtime inference optimization technique that splits a long input request so that it doesn’t monopolize the whole GPU. Keep in mind this is all within the context of vLLM. And since vLLM is an inference engine that's meant to serve a model to multiple concurrent users, having a GPU that’s fully monopolized on a single user's request means other users' requests would be in queue waiting to be processed. It isn’t too good to have the whole GPU occupied on a single request when the GPU is meant to be shared! So the key idea behind chunked prefill is to break the long request into smaller chunks, so that each chunk along with other users' requests gets processed and written into the KV cache together. Suppose we split up the long request into chunks and each chunk has 8 tokens. Now each memory block can hold 4 tokens. Therefore, 8 tokens can fit into 2 blocks of memory. After the first forward pass, 2 blocks are occupied, and after the second forward pass, 4 blocks of memory are occupied and so forth. Each forward pass handles a small chunk of the long request so that there's room in the same pass to keep serving other users' requests. Here's a small animation that I made today to fully visualize the idea behind chunked prefill when learning this topic~
0:18

Day 12/90 of Inference Engineering What is chunked prefill within vLLM? In continuation of yesterday's post on the high level architecture of vLLM, I want to dive deeper into vLLM core engine starting with the mechanics of chunked prefill. In this post, I will closely follow the original blog on the anatomy of vLLM. To start, let's define chunked prefill. It's a runtime inference optimization technique that splits a long input request so that it doesn’t monopolize the whole GPU. Keep in mind this is all within the context of vLLM. And since vLLM is an inference engine that's meant to serve a model to multiple concurrent users, having a GPU that’s fully monopolized on a single user's request means other users' requests would be in queue waiting to be processed. It isn’t too good to have the whole GPU occupied on a single request when the GPU is meant to be shared! So the key idea behind chunked prefill is to break the long request into smaller chunks, so that each chunk along with other users' requests gets processed and written into the KV cache together. Suppose we split up the long request into chunks and each chunk has 8 tokens. Now each memory block can hold 4 tokens. Therefore, 8 tokens can fit into 2 blocks of memory. After the first forward pass, 2 blocks are occupied, and after the second forward pass, 4 blocks of memory are occupied and so forth. Each forward pass handles a small chunk of the long request so that there's room in the same pass to keep serving other users' requests. Here's a small animation that I made today to fully visualize the idea behind chunked prefill when learning this topic~

max fu

28,891 Aufrufe • vor 9 Tagen

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓
0:11

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓

shmidt

36,446 Aufrufe • vor 27 Tagen

seedance 2.0 + my v2 AI UGC prompting system is giving insane results i spent the last 24 hours generating over 200 seedance 2.0 videos to figure out the best prompting framework system for AI UGC this video was made with 1 prompt and 1 tool, no editing was done to the video this was just a prompt to a video this is by far the best model i've ever used and the craziest part is that it can be fully automated this is the first time we can actually automate high quality ai ugc at this level bytedance owns tiktok so this model is trained on millions of high quality ugc videos. you just need to know how to extract that and call it in your prompt. we are so early... it's insane
0:14

seedance 2.0 + my v2 AI UGC prompting system is giving insane results i spent the last 24 hours generating over 200 seedance 2.0 videos to figure out the best prompting framework system for AI UGC this video was made with 1 prompt and 1 tool, no editing was done to the video this was just a prompt to a video this is by far the best model i've ever used and the craziest part is that it can be fully automated this is the first time we can actually automate high quality ai ugc at this level bytedance owns tiktok so this model is trained on millions of high quality ugc videos. you just need to know how to extract that and call it in your prompt. we are so early... it's insane

Miko

81,141 Aufrufe • vor 5 Monaten

✨ Every time the video models get better, the try on model on Photo AI also becomes a lot more useful, as a large % of my customers now are e-commerce store And showing clothes in a video is nice for sales! With AI this means stores don't need to do expensive shoots flying a model and entire camera and light crew around the world They can just upload a few photos of their models, then upload the clothes, and describe the setting (like a beach in Thailand) and in less than 10 seconds it's generated, for a video in less than a minute! Below is the input: a dress laid flat, and output: a full video shoot
0:10

✨ Every time the video models get better, the try on model on Photo AI also becomes a lot more useful, as a large % of my customers now are e-commerce store And showing clothes in a video is nice for sales! With AI this means stores don't need to do expensive shoots flying a model and entire camera and light crew around the world They can just upload a few photos of their models, then upload the clothes, and describe the setting (like a beach in Thailand) and in less than 10 seconds it's generated, for a video in less than a minute! Below is the input: a dress laid flat, and output: a full video shoot

@levelsio

334,170 Aufrufe • vor 1 Jahr

AI Is Moving Beyond “Generating Videos” — Toward “Generating Worlds” Over the past two years, AI video models have advanced at an astonishing pace. From Runway and Pika to Sora and Veo, AI-generated videos have become increasingly realistic and more consistent with the physical laws of the real world. Many people believe the next objective is simply to generate videos that are longer, sharper, and more lifelike. But if we take a step back, we can see that the real transformation is not happening in video itself. It is happening in world models. What Is a World Model? In 1943, psychologist Kenneth Craik proposed an idea that would influence artificial intelligence research for decades. He argued that the human brain does not merely react to the outside world. Instead, it maintains an internal model of how the world works. Because we have this internal model, we can predict the outcome of an action before we actually take it. Before crossing a road, we estimate whether a car will pass by. Before catching a ball, we predict its trajectory. These abilities come from continuously simulating the world in our minds, rather than relying entirely on trial and error. This idea later became known by a more formal term: World Model. A world model does not describe a single image or a fixed video clip. It is an internal representation capable of continuously simulating the rules and dynamics of the real world. Why Is AI Research Turning Toward World Models? Because predicting “what comes next” is becoming increasingly central to how AI systems work. Language models predict the next token. Image models predict the next step in the denoising process. Video models predict the next frame. A world model, however, attempts to predict something broader: What should the world look like in the next moment? In 2018, David Ha and Jürgen Schmidhuber proposed in their paper World Models that an intelligent agent could first learn a model of the world, and then use that internal model to plan its actions. The Dreamer series later demonstrated that many complex tasks could be learned by training agents inside an “imagined world.” At the same time, the development of video models such as Sora and Veo led researchers to another realization: A model capable of continuously generating video has already learned, at least implicitly, many of the rules governing the real world. As a result, these two research directions have gradually begun to converge. But Video Is Not Yet a World This is where the distinction is often misunderstood. For a world model to support meaningful real-time interaction, it must solve several critical problems. Most video models today are essentially answering one question: What should the next frame look like? A true world model needs to answer much more: What happens if I take one step forward? If I walk behind a building and then return, will the building still be there? If I suddenly change the camera angle, will the entire space remain consistent? If I enter a command such as: “Summon a dragon.” Will the world respond immediately? In other words, a world model must do more than generate content. It must understand space. It must understand time. It must understand causality. And it must understand interaction. Moving from watching to participating is where the real difficulty of world models begins. World Models Are Entering the Interactive Era One of the latest attempts in this direction is Alaya World, recently open-sourced by Alaya World, or Alaya Lab. Instead of generating a fixed video clip, it generates a world that users can explore in real time. Users can begin with text, an image, or a video, enter the generated scene, move freely through it, and introduce new prompts at any moment during generation. The world responds immediately. According to the publicly released information, Alaya World provides: Real-time streaming generation at 720p and 24 FPS Stable continuous exploration for more than one minute The ability to switch prompts and trigger skills or events during generation Model weights and inference code released under the Apache 2.0 License Training code and datasets planned for future release What makes these capabilities important is not simply the technical specifications. It is that the generated “world” can now support continuous interaction. The official demo shows that users can genuinely control, transform, and explore the generated environment. AI Is Evolving From a Tool Into an Environment Over the past few years, most discussions around AI have focused on content generation. Generating text. Generating images. Generating videos. But world models raise a fundamentally different question: Can AI generate an environment that people can inhabit, explore, and continuously evolve? If the answer is yes, the impact will extend far beyond video generation. Game development, robotics training, embodied intelligence, digital twins, virtual production, and many other fields could be transformed by the development of world models. World models are still at a very early stage. Yet from Craik’s proposal of an internal mental model more than eighty years ago to the emergence of today’s interactive world-generation systems, a clear evolutionary path is beginning to take shape. Perhaps what AI is ultimately learning has never been limited to images, videos, or language. Perhaps it is learning the world itself. References GitHub: Technical Report:
0:10

AI Is Moving Beyond “Generating Videos” — Toward “Generating Worlds” Over the past two years, AI video models have advanced at an astonishing pace. From Runway and Pika to Sora and Veo, AI-generated videos have become increasingly realistic and more consistent with the physical laws of the real world. Many people believe the next objective is simply to generate videos that are longer, sharper, and more lifelike. But if we take a step back, we can see that the real transformation is not happening in video itself. It is happening in world models. What Is a World Model? In 1943, psychologist Kenneth Craik proposed an idea that would influence artificial intelligence research for decades. He argued that the human brain does not merely react to the outside world. Instead, it maintains an internal model of how the world works. Because we have this internal model, we can predict the outcome of an action before we actually take it. Before crossing a road, we estimate whether a car will pass by. Before catching a ball, we predict its trajectory. These abilities come from continuously simulating the world in our minds, rather than relying entirely on trial and error. This idea later became known by a more formal term: World Model. A world model does not describe a single image or a fixed video clip. It is an internal representation capable of continuously simulating the rules and dynamics of the real world. Why Is AI Research Turning Toward World Models? Because predicting “what comes next” is becoming increasingly central to how AI systems work. Language models predict the next token. Image models predict the next step in the denoising process. Video models predict the next frame. A world model, however, attempts to predict something broader: What should the world look like in the next moment? In 2018, David Ha and Jürgen Schmidhuber proposed in their paper World Models that an intelligent agent could first learn a model of the world, and then use that internal model to plan its actions. The Dreamer series later demonstrated that many complex tasks could be learned by training agents inside an “imagined world.” At the same time, the development of video models such as Sora and Veo led researchers to another realization: A model capable of continuously generating video has already learned, at least implicitly, many of the rules governing the real world. As a result, these two research directions have gradually begun to converge. But Video Is Not Yet a World This is where the distinction is often misunderstood. For a world model to support meaningful real-time interaction, it must solve several critical problems. Most video models today are essentially answering one question: What should the next frame look like? A true world model needs to answer much more: What happens if I take one step forward? If I walk behind a building and then return, will the building still be there? If I suddenly change the camera angle, will the entire space remain consistent? If I enter a command such as: “Summon a dragon.” Will the world respond immediately? In other words, a world model must do more than generate content. It must understand space. It must understand time. It must understand causality. And it must understand interaction. Moving from watching to participating is where the real difficulty of world models begins. World Models Are Entering the Interactive Era One of the latest attempts in this direction is Alaya World, recently open-sourced by Alaya World, or Alaya Lab. Instead of generating a fixed video clip, it generates a world that users can explore in real time. Users can begin with text, an image, or a video, enter the generated scene, move freely through it, and introduce new prompts at any moment during generation. The world responds immediately. According to the publicly released information, Alaya World provides: Real-time streaming generation at 720p and 24 FPS Stable continuous exploration for more than one minute The ability to switch prompts and trigger skills or events during generation Model weights and inference code released under the Apache 2.0 License Training code and datasets planned for future release What makes these capabilities important is not simply the technical specifications. It is that the generated “world” can now support continuous interaction. The official demo shows that users can genuinely control, transform, and explore the generated environment. AI Is Evolving From a Tool Into an Environment Over the past few years, most discussions around AI have focused on content generation. Generating text. Generating images. Generating videos. But world models raise a fundamentally different question: Can AI generate an environment that people can inhabit, explore, and continuously evolve? If the answer is yes, the impact will extend far beyond video generation. Game development, robotics training, embodied intelligence, digital twins, virtual production, and many other fields could be transformed by the development of world models. World models are still at a very early stage. Yet from Craik’s proposal of an internal mental model more than eighty years ago to the emergence of today’s interactive world-generation systems, a clear evolutionary path is beginning to take shape. Perhaps what AI is ultimately learning has never been limited to images, videos, or language. Perhaps it is learning the world itself. References GitHub: Technical Report:

雪踏乌云

112,114 Aufrufe • vor 11 Tagen

🚨NEWS: $TSLA DEVELOPING NEW SMALLER, CHEAPER EV SUV • Tesla is developing an all-new compact electric SUV, according to four people familiar with the matter. • The vehicle is not a variant of the Model 3 or Model Y. ✅ Key Details • Length: approximately 4.28 meters (14 feet) — significantly shorter than the Model Y (about 15.7 feet). • Planned production locations: primarily China (Shanghai factory), with potential expansion to the United States and Europe. • Expected pricing: substantially lower than the entry-level Model 3 (which starts at ~$37,000 in the US and $34,000 in China). ✅ Design Approach • Smaller battery for cost reduction (resulting in shorter range than the Model Y’s 306–327 miles). • Single electric motor instead of dual motors. • Significantly lighter weight target (~1.5 metric tons vs. ~2 tons for Model Y). ✅ Strategic Context • This project comes after Elon Musk scrapped a previous low-cost EV plan in 2024 to focus on robotaxis and Optimus. • The new SUV could be offered in both fully autonomous and human-driven versions to suit different global markets and regulations. • The development is still in early stages, with production unlikely to start in 2026.
0:11

🚨NEWS: $TSLA DEVELOPING NEW SMALLER, CHEAPER EV SUV • Tesla is developing an all-new compact electric SUV, according to four people familiar with the matter. • The vehicle is not a variant of the Model 3 or Model Y. ✅ Key Details • Length: approximately 4.28 meters (14 feet) — significantly shorter than the Model Y (about 15.7 feet). • Planned production locations: primarily China (Shanghai factory), with potential expansion to the United States and Europe. • Expected pricing: substantially lower than the entry-level Model 3 (which starts at ~$37,000 in the US and $34,000 in China). ✅ Design Approach • Smaller battery for cost reduction (resulting in shorter range than the Model Y’s 306–327 miles). • Single electric motor instead of dual motors. • Significantly lighter weight target (~1.5 metric tons vs. ~2 tons for Model Y). ✅ Strategic Context • This project comes after Elon Musk scrapped a previous low-cost EV plan in 2024 to focus on robotaxis and Optimus. • The new SUV could be offered in both fully autonomous and human-driven versions to suit different global markets and regulations. • The development is still in early stages, with production unlikely to start in 2026.

Tsla Archive

56,232 Aufrufe • vor 3 Monaten

MiniMax M2.5 is benchmaxed. I gave 4 models the same prompt: Create a neon "OPEN" sign in HTML. GLM 5: Clean, classic neon. Nailed it. Claude Opus 4.6: Stylized with glow. Solid. Gemini 3 Pro: Cursive with bloom lighting. Creative. MiniMax M2.5: Spelled it "O b∈ N" with broken spacing. This model ranks #2 on BridgeBench with a 59.7 score and 100% completion rate. But it can't spell a 4-letter word. Benchmarks don't tell the whole story. A model can ace structured tasks and fail basic creative prompts. High score ≠ production ready.
0:15

MiniMax M2.5 is benchmaxed. I gave 4 models the same prompt: Create a neon "OPEN" sign in HTML. GLM 5: Clean, classic neon. Nailed it. Claude Opus 4.6: Stylized with glow. Solid. Gemini 3 Pro: Cursive with bloom lighting. Creative. MiniMax M2.5: Spelled it "O b∈ N" with broken spacing. This model ranks #2 on BridgeBench with a 59.7 score and 100% completion rate. But it can't spell a 4-letter word. Benchmarks don't tell the whole story. A model can ace structured tasks and fail basic creative prompts. High score ≠ production ready.

BridgeMind

54,212 Aufrufe • vor 5 Monaten

i spent $26,600 on cloud GPU rentals over 14 months before i found a NVIDIA DGX Spark at $2,999 (founder's edition) or $3,999 (shipping price) it paid for itself in 6 weeks i run 200B parameter models locally now and my old cloud provider keeps sending me loyalty discount emails the math on that $26,600 is embarrassing to type out loud $1,900/month for 14 months, H100 instances on a specialist cloud provider, because anything bigger than a 70B model simply would not fit anywhere else i paid the invoices like they were a utility bill and told myself it was just the cost of doing serious AI work it took me over a year to find out it wasn't 14 months, broken down: → months 1-4: $1,400-1,600/month - felt like manageable infrastructure overhead → months 5-9: crept to $1,900-2,100 as i started running DeepSeek-class experiments, costs tracking directly with model size → months 10-12: one agent loop ran for 36 hours against a 130B model while i slept, that month hit $2,400 → month 13: ran the cumulative total for the first time, saw $23,800, felt physically sick → month 14: another $2,800 month while i waited for the hardware to ship the box is the NVIDIA DGX Spark - roughly the footprint of a large mac mini, powered by a GB10 Grace Blackwell chip with 128GB of unified LPDDR5X memory that unified memory is the whole thing an RTX 4090 has 24GB of VRAM, which means a 70B model in full BF16 precision physically does not fit, you're quantizing down or you're renting cloud, those are your options this box loads a 200B parameter model quantized and serves it through vLLM over localhost, same API interface the cloud endpoint used the migration took one line of code - i changed the base URL from the provider's endpoint to 127.0.0.1:8000 and everything just worked electricity to run continuous 200B inference locally comes out to about $12/month the payback arithmetic is almost too clean: $2,999 hardware cost against $1,900/month saved, the box paid for itself before i'd owned it two months what i didn't account for was how completely the cost model changes your behavior when there's no hourly meter running, you greenlight experiments you'd never approve on cloud - agent loops that churn for hours, running 10,000 documents through a reasoning pass at 3am, speculative fine-tuning jobs you'd normally skip because the cost felt unjustifiable i ran more experiments in the first 30 days after the box arrived than in the four months before it the loyalty discount email landed about 8 weeks after i cancelled the cloud subscription 15% off my next three months, valued customer, we'd love to have you back i didn't reply the box was already running
0:15

i spent $26,600 on cloud GPU rentals over 14 months before i found a NVIDIA DGX Spark at $2,999 (founder's edition) or $3,999 (shipping price) it paid for itself in 6 weeks i run 200B parameter models locally now and my old cloud provider keeps sending me loyalty discount emails the math on that $26,600 is embarrassing to type out loud $1,900/month for 14 months, H100 instances on a specialist cloud provider, because anything bigger than a 70B model simply would not fit anywhere else i paid the invoices like they were a utility bill and told myself it was just the cost of doing serious AI work it took me over a year to find out it wasn't 14 months, broken down: → months 1-4: $1,400-1,600/month - felt like manageable infrastructure overhead → months 5-9: crept to $1,900-2,100 as i started running DeepSeek-class experiments, costs tracking directly with model size → months 10-12: one agent loop ran for 36 hours against a 130B model while i slept, that month hit $2,400 → month 13: ran the cumulative total for the first time, saw $23,800, felt physically sick → month 14: another $2,800 month while i waited for the hardware to ship the box is the NVIDIA DGX Spark - roughly the footprint of a large mac mini, powered by a GB10 Grace Blackwell chip with 128GB of unified LPDDR5X memory that unified memory is the whole thing an RTX 4090 has 24GB of VRAM, which means a 70B model in full BF16 precision physically does not fit, you're quantizing down or you're renting cloud, those are your options this box loads a 200B parameter model quantized and serves it through vLLM over localhost, same API interface the cloud endpoint used the migration took one line of code - i changed the base URL from the provider's endpoint to 127.0.0.1:8000 and everything just worked electricity to run continuous 200B inference locally comes out to about $12/month the payback arithmetic is almost too clean: $2,999 hardware cost against $1,900/month saved, the box paid for itself before i'd owned it two months what i didn't account for was how completely the cost model changes your behavior when there's no hourly meter running, you greenlight experiments you'd never approve on cloud - agent loops that churn for hours, running 10,000 documents through a reasoning pass at 3am, speculative fine-tuning jobs you'd normally skip because the cost felt unjustifiable i ran more experiments in the first 30 days after the box arrived than in the four months before it the loyalty discount email landed about 8 weeks after i cancelled the cloud subscription 15% off my next three months, valued customer, we'd love to have you back i didn't reply the box was already running

Argona

22,099 Aufrufe • vor 1 Monat

Ever wondered if you could extract capabilities and behaviors from neural networks and reuse/update/route it as needed? We introduce low-rank circuit conditioning, a novel approach that preserves the model's output behavior while reshaping how an existing capability is represented. In the base model, standard compact recovery stalls at 29%. After conditioning, the same extraction pipeline reaches 91.33% autoregressive full-answer recovery from 5.05% of MLP channels. The evidence points to a possibility of extracting and using isolated capabilities saving cost, latency and high adaptability. Read our work to understand more -
0:11

Ever wondered if you could extract capabilities and behaviors from neural networks and reuse/update/route it as needed? We introduce low-rank circuit conditioning, a novel approach that preserves the model's output behavior while reshaping how an existing capability is represented. In the base model, standard compact recovery stalls at 29%. After conditioning, the same extraction pipeline reaches 91.33% autoregressive full-answer recovery from 5.05% of MLP channels. The evidence points to a possibility of extracting and using isolated capabilities saving cost, latency and high adaptability. Read our work to understand more -

tokenbender

45,240 Aufrufe • vor 2 Monaten

A 17-year-old student replaced $850 in monthly AI bills with 1 tiny NVIDIA box and never looked at cloud invoices the same way again. The machine cost $4,699. That sounded expensive until the math started winning. Cloud GPUs charge every experiment. Every failed prompt. Every forgotten instance. Every late-night demo. A local AI box flips the model. Private documents stay on your desk. Coding agents run without API anxiety. RAG, embeddings and model testing stop burning money by the hour. One $3K to $10K client project can cover most of the hardware. After that, every new workflow becomes cheaper to build. The next AI advantage isn’t finding a better model. It’s owning the computer that runs it.
0:11

A 17-year-old student replaced $850 in monthly AI bills with 1 tiny NVIDIA box and never looked at cloud invoices the same way again. The machine cost $4,699. That sounded expensive until the math started winning. Cloud GPUs charge every experiment. Every failed prompt. Every forgotten instance. Every late-night demo. A local AI box flips the model. Private documents stay on your desk. Coding agents run without API anxiety. RAG, embeddings and model testing stop burning money by the hour. One $3K to $10K client project can cover most of the hardware. After that, every new workflow becomes cheaper to build. The next AI advantage isn’t finding a better model. It’s owning the computer that runs it.

Lummox

321,288 Aufrufe • vor 9 Tagen

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish
0:19

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish

KingWilliam

12,305 Aufrufe • vor 1 Monat

this is f**king dangerous someone figured out how to make Opus 4.8 run on Fable 5's brain with one prompt access to the best model is never guaranteed. It disappeared once already this year. but you can use it forever. here's how: 1. ask Fable 5: "write the operating manual your replacement will run on" (procedures, failure modes, a 5-question self-test) 2. save the output as one .md file and drop it into a new Claude Project as the project instructions 3. switch to Opus 4.8 and now your everyday model runs off the smart one's method, no top-tier price save and bookmark this no matter what full extraction prompt is in the article below: ↓
0:18

this is f**king dangerous someone figured out how to make Opus 4.8 run on Fable 5's brain with one prompt access to the best model is never guaranteed. It disappeared once already this year. but you can use it forever. here's how: 1. ask Fable 5: "write the operating manual your replacement will run on" (procedures, failure modes, a 5-question self-test) 2. save the output as one .md file and drop it into a new Claude Project as the project instructions 3. switch to Opus 4.8 and now your everyday model runs off the smart one's method, no top-tier price save and bookmark this no matter what full extraction prompt is in the article below: ↓

Hamza Khalid

32,300 Aufrufe • vor 18 Tagen