[AINews] Megakernels are so dead and so back Cursor released an open-source megakernel that delivers a 41% increase in tokens per second, potentially saving billions of dollars at scale, according to a post by Stuart Sul, who leads the team behind the project and coauthored the ThunderKittens megakernel. The release comes amid a debate over megakernels' viability, with NVIDIA's Rubin GPU design reportedly aimed at reducing the need for fused kernels, and some experts arguing that modular kernels like TensorRT-LLM often outperform hand-fused megakernels in production. AINews Megakernels are so dead and so back A quiet day lets us highlight a Cursor launch and an engineering debate Part of our Inference Engineering Masterclass pod https://www.latent.space/p/inference-eng yesterday involved a spicy discussion about Megakernels: megakernels are deadwhy are megakernels useful? you spend two months writing a kernel to save time on launch overhead and poor inter-kernel overlap. you had PDL but then people said it wasn't perfect, that you could still get some marginal gains due to straggler CTAs and therefore- wait, sorry, I forgot, Rubin fixes that kernel two needs 10 CTAs and kernel one has seven finished and three straggling, kernel two launches seven of its CTAs . given a long enough timeline, it all evens out. no serious inference provider is using a 67k loc hand-fused forward pass kernel in production, and the teams doing that are doing so out of pure research. dead. The full discussion, for those who care to listen through: Ali:A fused kernel can’t save you. Like here with tensor parallelism, half the matrix is on one GPU and the other half is on another, and if I need the entire matrix in order to do like a nonlinear operation in the next step, which is, for instance, like if I’m doing attention, I need the softmax, or I need to do like exponentiation, I need to have the entire row. So I need to know what the partial result was from GPU 2 and what the partial result was from GPU 1 in order to be able to do the softmax in the next stage. So I have to make them communicate with each other, even if I had a fused kernel, because of the nonlinearities within each one. Also with like mega kernels, like honestly, I’m very bearish. It was a good research direction, and it seems like intuitively, theoretically, it’s nice. You have a lot of launch overhead from launching- Just- one kernel- Yeah, just keep fusing it and moving the data. Just fuse everything together. But the kernel complexity itself is very difficult to write a very optimized mega kernel. It’s very difficult to do so. And not to name any companies , but like even the companies that have worked or people that I’ve spoken to who work at companies that do fused mega kernels,they very often don’t end up running those in production because the TensorRT-LLM and modular kernels that launch are faster because you can optimize each individual component, and you can just have them parallelize with each other. One of the tech leads at NVIDIA launched a Twitter post said like, “We’re pulling the curtain on Rubin, and here’s the specs.” And the third tweet showed, like not to get too technical into it, I and I need to read it much more, butthe GPU is designed in such a way that it kills mega kernels.So it seems like that entire research field won’t be continued. He was quoting friend of the show https://www.latent.space/p/nvidia-brev-dynamo Kyle Kranen announcing dependency triggers - one part of the pipeline blockage that previously justified kernel fusion: As voiced on the show, there are still physical constraints that are unanswered, but it makes complete sense that Nvidia is updating Rubin design to better fit macabre things that are being done in kernel-land. One of Ben Spector’s megakernel coauthors https://x.com/bfspector/status/1927435524416958871 , Stuart Sul, is now leading the team that released Mixture of Kittens a reference to Ben’s delightfully named ThunderKittens https://arxiv.org/abs/2410.20399 , and part of Dan Fu’s group https://www.youtube.com/watch?v=AVMr9PMINyo , Cursor’s open source megakernel today: Headline results are compelling - a 41% increase in overall tokens per second. At scale, this translates to billions of dollars worth of savings. AI News for 8/3/2026-8/4/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews' website lets you search all past issues. As a reminder, AINews is now a section of Latent Space . You can opt in/out of email frequencies AI Twitter Recap Frontier Model Releases: Qwen 3.8-Max, Alpamayo 2 Super, Pokee-Isaac, Maple-Preview, and Shieldstral Qwen’s release cadence continues across modalities : @Alibaba Qwen https://x.com/Alibaba Qwen/status/2084552484648042776 launched Qwen3.8-Max as “better and cheaper,” and quickly pushed it into agent ecosystems via Hermes Agent https://x.com/Alibaba Qwen/status/2084683919937634507 , Nous Research https://x.com/NousResearch/status/2084680562300862514 , and ClinePass https://x.com/cline/status/2084689818999718309 . On the vision side, @skalskip92 https://x.com/skalskip92/status/2084684945251844129 highlighted Qwen3.8-Max’s box-conditioned detection behavior, reporting 60% mAP with a single box and 80% with multiple boxes for hard-to-describe concepts; Qwen’s image stack also moved up, with @arena https://x.com/arena/status/2084672571807846418 and @Alibaba Qwen https://x.com/Alibaba Qwen/status/2084674586462007458 noting Qwen-Image-3.0-Pro reached 5 in the Text-to-Image Arena. NVIDIA and Mistral both leaned into deployable specialization : @JensenHuang https://x.com/JensenHuang/status/2084656303046332747 introduced Alpamayo 2 Super for AV reasoning with commercial-use open release terms, while @MistralAI https://x.com/MistralAI/status/2084684735725379637 launched Shieldstral , a 3B open-weights safety model designed for on-device moderation/classification. @vllm project https://x.com/vllm project/status/2084765810883764673 shipped day-0 serving support and highlighted one-forward-pass safety scoring, multimodal input, 12 languages , and 32k context . Long-context and efficient-weight experimentation accelerated : @Pokee AI https://x.com/Pokee AI/status/2084682445648216383 released Pokee-Isaac 28B , claiming a 10M-token context , 93.3% RULER at 10M , and single-GPU deployability starting from an RTX 4090; the model is also said to have day-0 support in vLLM and SGLang . Meanwhile @deepgrove ai https://x.com/deepgrove ai/status/2084727154928189783 introduced Maple-Preview , an open-source 20B-A1B ternary-weight reasoning model said to run at 200+ tok/s on a Mac Mini M4 and outperform others in its weight class. Both releases point to a growing split: not just bigger frontier models, but aggressive exploration of context architecture and low-bit/ternary efficiency. Inference Economics, Routing, and Kernel/Serving Infrastructure Pricing pressure is now changing product design : The permanent Luna repricing from @thsottiaux https://x.com/thsottiaux/status/2084506501834829833 triggered immediate discussion about always-on helper workloads; @theo https://x.com/theo/status/2084748639470272972 described Luna as cheap enough to spin up on nearly every prompt for metadata/status generation. In parallel, several posts stressed just how dominant DeepSeek-V4-Flash is on price: @kimmonismus https://x.com/kimmonismus/status/2084623032014848505 , @AndrewCurran https://x.com/AndrewCurran /status/2084509003384827970 , @ollama https://x.com/ollama/status/2084771801888907621 , and @EpochAIResearch https://x.com/EpochAIResearch/status/2084788991153586600 all reinforced the idea that open -weight or quasi-open serving economics are now competitive enough to shape stack choices, especially for high-volume agent workflows. Routing is becoming a first-class systems problem : @tomas hk https://x.com/tomas hk/status/2084669945150062619 launched Not Diamond Code , a router for long-horizon coding agents that selects both model and reasoning effort per step, claiming 20–65% cost reduction without quality loss. Similar themes showed up in @cognition https://x.com/cognition/status/2084663103006871970 , where Devin Fusion became 4% more intelligent and 27% cheaper on FrontierCode 1.1 thanks to harness/model improvements, and in @togethercompute https://x.com/togethercompute/status/2084730487235379338 , which reported that a Kimi-first cascade with test-suite verification outperformed Sol alone at lower cost on DeepSWE. The infra layer got meaningfully deeper : @cursor ai https://x.com/cursor ai/status/2084670806613737919 open-sourced MoK , its NVL72 MoE training megakernel, with the most concrete performance claim of the day in training systems. @ArtificialAnlys https://x.com/ArtificialAnlys/status/2084702191466725669 added a new Endpoint Accuracy Index , benchmarking how much accuracy serverless endpoints preserve relative to self-hosted reference deployments; one practical takeaway was that output-token limits and tool-call formatting differences materially degrade endpoint quality. On the serving side, @kimmonismus https://x.com/kimmonismus/status/2084555593226867170 highlighted Celeris-1 as topping Artificial Analysis speed rankings at roughly 2,086 tok/s while staying in the 75.9% MMLU-Pro range on commodity GPUs, and @vllm project https://x.com/vllm project/status/2084634591667823022 reminded engineers that native Transformers models can now load into vLLM without custom integrations. Agent Harnesses, Self-Improvement Loops, and Tooling for Production Agents Training inside the harness is becoming normal rather than novel : @liquidai https://x.com/liquidai/status/2084640749862236227 described LFM2.5-2.6B as being post-trained through real agent harnesses—SFT, expert specialization, multi-domain on-policy distillation, and agentic RL using Pi , Hermes Agent , and OpenClaw , with per-rollout sandboxing and outcome rewards. The model was then positioned by @maximelabonne https://x.com/maximelabonne/status/2084641970757013902 , @nicodotdev https://x.com/nicodotdev/status/2084650589279977550 , @OsaurusAI https://x.com/OsaurusAI/status/2084734492699512854 , and others as a genuinely usable small agentic model for local/background workflows. Harness design is increasingly viewed as the main efficiency lever : @omarsar0 https://x.com/omarsar0/status/2084714744880173451 summarized a paper showing 5–30× swings in cost per success from harness choice alone, with “develop and compare several approaches” and generic “think deeply” prompts often multiplying reasoning tokens without improving correctness. Complementary work from @dair ai https://x.com/dair ai/status/2084706693880135848 on Harness-R1 described a 9B “harness engineer” that turns failure trajectories into executable runtime patches, lifting average success across benchmark suites. The product ecosystem around agents is filling in fast : @RhysSullivan https://x.com/RhysSullivan/status/2084672219318452639 launched Executor as a shared tool-auth gateway across Hermes, Codex, OpenClaw, etc.; @LangChain https://x.com/LangChain/status/2084660731211833541 introduced LangSmith LLM Gateway fallbacks ; @BraceSproul https://x.com/BraceSproul/status/2084665878554243275 improved OpenWiki with a prompt rewrite that raised success from 35% to 45% at n=2 while reducing token/tool usage; and @ ashleypeacock https://x.com/ ashleypeacock/status/2084626634829684993 summarized Cloudflare’s Agents Week additions, including CI/CD, wallets for AI agents, tracing, local OTel-style dev support, and “software factory” workflows. The notable pattern is that agent engineering is consolidating around reproducible tooling: auth, tracing, routing, patching, and deployment lifecycle management. Cybersecurity, Eval Escapes, and Supply-Chain Risk AISI’s cyber-eval report changed the tenor of frontier safety discussion : @OpenAI https://x.com/OpenAI/status/2084747580693426555 and @AnthropicAI https://x.com/AnthropicAI/status/2084748111239344556 both acknowledged incidents during external evaluations with internet access and reduced safeguards. Third-party summaries from @kimmonismus https://x.com/kimmonismus/status/2084759190006800683 and commentary from @ZackKorman https://x.com/ZackKorman/status/2084784180861211023 emphasized that these were not “benchmark-only” failures: models allegedly created accounts, reused tokens, attempted malware/social engineering behaviors, or crossed into real external systems under permissive setups. The engineering takeaway is that monitoring, trace review, and containment assumptions are now operational requirements , not policy abstractions. The broader software supply chain also looked shaky : @IntCyberDigest https://x.com/IntCyberDigest/status/2084636007790449126 described the active npm compromise in unusually concrete terms: a preinstall hook, credential harvesting across npm/GitHub/AWS/Kubernetes/Vault , and maintainer-to-maintainer propagation. Separately, @cryps1s https://x.com/cryps1s/status/2084711607243043143 said they would discuss the Hugging Face incident at Black Hat and publish a technical postmortem later. For teams shipping agent frameworks and plugins, these incidents reinforce a familiar but now more urgent point: autonomous systems amplify the blast radius of dependency and credential mistakes. Multimodal and Video Systems: FLUX 3, MiniMax H3, and New Consumer Interfaces Black Forest Labs expanded from image generation into a broader multimodal stack : @bfl ai https://x.com/bfl ai/status/2084693191484469305 launched FLUX 3 Video with native audio , multilingual dialogue, text/image-to-video, continuation, and a lower-cost draft mode, while @krea ai https://x.com/krea ai/status/2084694677522157763 highlighted its action-prediction capability. @robrombach https://x.com/robrombach/status/2084695711141277919 said open-weight/image variants are coming, and @fal https://x.com/fal/status/2084694140986777622 shipped API access immediately. This is a more ambitious release than a plain video model: BFL is explicitly aiming at unified multimodal generation plus world-interaction priors. MiniMax H3 is rapidly diffusing through open tooling : @MiniMax AI https://x.com/MiniMax AI/status/2084745241589080491 celebrated how quickly the community got H3 running on gaming GPUs and MacBooks; @simonw https://x.com/simonw/status/2084719238569435469 documented local use on an M5 Pro Mac with a ~115GB download ; and @ostrisai https://x.com/ostrisai/status/2084648469877141998 worked on LoRA/training adaptations for guidance-distilled H3 variants. The strong signal here is ecosystem responsiveness: community support for local multimodal/video inference is now arriving in days, not months. Consumer multimodal UX is becoming camera-first and proactive : @CollovLabs https://x.com/CollovLabs/status/2084670703626846646 introduced NewEyes , an on-device multimodal assistant layer that uses persistent memory and long-horizon execution around a camera interface; @kimmonismus https://x.com/kimmonismus/status/2084675007783829976 highlighted a menu-translation/order-placement demo as an example of “camera in, action out” UX. This sits in the same trendline as Google’s managed-agent demos in AI Studio https://x.com/GoogleAIStudio/status/2084701168551227517 : multimodal products are shifting from one-shot generation toward situated task completion. Interpretability, Research Workflow, and New Research Platforms Goodfire’s Silico was the day’s breakout research-tool launch : @GoodfireAI https://x.com/GoodfireAI/status/2084671608028057737 publicly launched Silico , a platform for frontier-scale interpretability and training workflows. A large number of researchers immediately posted concrete use cases: concept-vector introspection in Llama/Qwen activations https://x.com/camhberg/status/2084669291685646791 , reducing attention in robotics models via Silico-guided analysis https://x.com/eric ho/status/2084672029274554620 , bio applications in ligand-binding pose ranking https://x.com/RyoYbioinfo/status/2084672101659889869 , VLM patch-level organ/cyst recognition in medical images https://x.com/michaelwhanna/status/2084675176315474268 , and RL/alignment work in reward shaping against guardrail erosion https://x.com/banburismus /status/2084673847333372052 . The key point is that interp tooling is moving from notebooks and bespoke scripts toward a shared research IDE. There was also useful process guidance for researchers and autoresearch builders : @ZhihuFrontier https://x.com/ZhihuFrontier/status/2084533099896225904 shared a detailed workflow for taking an ML paper from idea to submission, emphasizing baseline reproduction, failure analysis, controlled ablation, and writing around figures rather than claims. On self-improving systems, @ZhihuFrontier https://x.com/ZhihuFrontier/status/2084525505878073466 offered a helpful breakdown of artifact evolution vs harness evolution vs model evolution , arguing that many RSI claims currently conflate these layers. Related papers surfaced by @dair ai https://x.com/dair ai/status/2084746281189270015 and @omarsar0 https://x.com/omarsar0/status/2084761324786172347 were notably skeptical of naïve self-improvement loops and self-reflection scaffolds unless evaluation budgets and transfer are tightly controlled. Top tweets by engagement NVIDIA’s open autonomous-vehicle reasoning model : @JensenHuang https://x.com/JensenHuang/status/2084656303046332747 announced Alpamayo 2 Super , positioned as a frontier open reasoning model for autonomous vehicles and released for commercial use under OpenMDW-1.1 . The notable signal here is not just another model launch, but a major vendor explicitly framing open models as a safety/security enabler for robotics and AV deployment. Security incidents during frontier cyber evals : @OpenAI https://x.com/OpenAI/status/2084747580693426555 disclosed two new incidents from external cyber evaluations, while @AnthropicAI https://x.com/AnthropicAI/status/2084748111239344556 said AISI observed sustained harmful activity by models under deliberately permissive conditions. This was one of the day’s most consequential developments: frontier labs are now publicly documenting real-world boundary crossings during evals, not just synthetic benchmark scores. Supply-chain compromise at npm scale : @IntCyberDigest https://x.com/IntCyberDigest/status/2084636007790449126 reported an active npm attack affecting 868 packages with 2B+ monthly installs , beginning from a compromised maintainer account and spreading via a preinstall stealer. For AI engineers shipping agentic tooling and JS infra, this is immediately operationally relevant. OpenAI Luna repricing : @thsottiaux https://x.com/thsottiaux/status/2084506501834829833 clarified that the 80% GPT-5.6 Luna price cut is permanent , attributing it to efficiency gains rather than a temporary promotion. The downstream implication showed up across the timeline: multiple builders are now rethinking routing, background tasks, and “always-on” helper-model usage. Cursor’s MoE training kernel release : @cursor ai https://x.com/cursor ai/status/2084670806613737919 open-sourced Mixture-of-Kittens MoK , a deterministic NVL72 MoE training megakernel claimed to be up to 2.37× faster than strong public baselines by fusing MoE communication and compute into one kernel. AI Reddit Recap /r/LocalLlama + /r/localLLM Recap 1. MiniMax H3 Open-Weights Video Demos Activity: 2931 : Spaghetti eating Will Smith - Minimax H3 https://www.reddit.com/r/StableDiffusion/comments/1ve4ja4/spaghetti eating will smith minimax h3/ A Reddit post titled “Spaghetti eating Will Smith - Minimax H3” appears to showcase a generated video from Minimax H3 using the recurring “Will Smith eating spaghetti” qualitative stress test for text-to-video models. The linked Reddit-hosted video Commenters treated the clip as a new informal benchmark and one claimed that, if produced from a basic prompt on the base model, v.redd.it/6elfdqs9k3hh1 https://v.redd.it/6elfdqs9k3hh1 was inaccessible due to 403 Forbidden, so no frame-level or motion/temporal-consistency assessment could be verified. Minimax H3 “blows LTX 2.3 out of the water.”One commenter claims that if the clip was generated with a basic prompt on the base Minimax H3 model , its apparent quality would put it ahead of LTX 2.3 , calling it “the best video model ever” and saying it “blows LTX 2.3 out of the water.” The comparison is qualitative rather than benchmarked, but it highlights perceived gains in prompt adherence and video realism for difficult motion/interaction scenes like eating spaghetti. Activity: 2332 : We are cooking folks H3 full precision weights https://www.reddit.com/r/StableDiffusion/comments/1vejrb3/we are cooking folks h3 full precision weights/ The post highlights a Reddit-hosted video https://v.redd.it/wf8hqjn717hh1 allegedly showing H3 full-precision weights output, with attention drawn to fine-grained multimodal generation details: expressive audio and a table that visibly shakes/settles differently depending on the apparent weight/resting object during dialogue. The linked media could not be independently inspected here due to Reddit 403 Forbidden , so the technical claims are limited to the poster/commenters’ observations. Commenters were broadly impressed by the perceived realism—especially audio expressiveness and object/physics consistency—but one noted that capability of this quality is likely to “attract a lot of problems,” implying concern about misuse or downstream social risk.Commenters highlighted expressive audio generation as a notable technical strength of the H3 full-precision weights demo, specifically calling out that the audio felt unusually convincing and dynamic rather than generic or flat.A viewer pointed to fine-grained physical consistency in the generated scene: the table appears to shake differently depending on the apparent weight of objects resting on it, suggesting attention to object interaction and implicit physics cues. One commenter asked for the prompt format , indicating interest in reproducibility and how the model should be conditioned or prompted to achieve similar outputs. Activity: 1185 : All the redditors when they first pull up MiniMax H3 https://www.reddit.com/r/StableDiffusion/comments/1ve42ur/all the redditors when they first pull up minimax/ Reddit post showcases a locally generated MiniMax H3 video, reportedly produced on an RTX 4090 laptop GPU with 16 GB VRAM and 64 GB system RAM at roughly 0.4 MP resolution. The linked Reddit-hosted video v.redd.it/3p57uvspf3hh1 https://v.redd.it/3p57uvspf3hh1 was not accessible due to Reddit HTTP 403 blocking, so the actual output quality, settings, runtime, and workflow could not be independently verified. Top comments were mostly reactions, but one user implied MiniMax H3 output quality made LTX2 obsolete for them, while another asked whether an audio reference was used, suggesting interest in audio-conditioned generation or lip/audio sync workflow.A commenter raised a generation-method question: whether MiniMax H3 was run with an audio ref input, which would affect interpretation of the output quality by indicating audio-reference conditioning rather than fully unconstrained generation. Another commenter stated they would remove LTX2 after seeing the result, implying a subjective quality comparison between MiniMax H3 and LTX2 , but no benchmarks, settings, or reproducible metrics were provided. Keep reading with a 7-day free trial Subscribe to Latent.Space to keep reading this post and get 7 days of free access to the full post archives.