Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Not every new model needs to be the biggest model. Sometimes I'd rather have one that's fast, reliable, affordable, and actually pleasant to build with. That's the impression I got after using Tencent Hunyuan Hy3. I threw a mix of coding, reasoning, and agent tasks at it throughout the...

FellMentKE's profile picture

FELIX

271,152 subscribers

56,379 Aufrufe • vor 1 Monat •via X (Twitter)

Wissenschaft & TechnologieBildung
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Tencent's Hy3 lands today with real coding and agent ability and a price that undercuts the models you'd put it against. It's a 295B MoE with only 21B active parameters, a big part of why it stays cheap to serve, plus a 256K context window and an Apache 2.0 license that even outperforms GLM-5.1 although GLM is 2.5x larger. On OpenRouter it runs at $0.14 per million input tokens and $0.58 per million output. For a model Tencent benchmarks against much larger flagships, that pricing is insane. Price-performance-ratio is China's real moat. I already wrote about Tencent Hy3 earlier and the significant leap in quality it represents. Therefore, I'm pleased to recommend this model from Tencent Hy. Open Router link down below: #Hy3 #Hunyuan #AICoding
0:45

Tencent's Hy3 lands today with real coding and agent ability and a price that undercuts the models you'd put it against. It's a 295B MoE with only 21B active parameters, a big part of why it stays cheap to serve, plus a 256K context window and an Apache 2.0 license that even outperforms GLM-5.1 although GLM is 2.5x larger. On OpenRouter it runs at $0.14 per million input tokens and $0.58 per million output. For a model Tencent benchmarks against much larger flagships, that pricing is insane. Price-performance-ratio is China's real moat. I already wrote about Tencent Hy3 earlier and the significant leap in quality it represents. Therefore, I'm pleased to recommend this model from Tencent Hy. Open Router link down below: #Hy3 #Hunyuan #AICoding

Chubby♨️

23,439 Aufrufe • vor 1 Monat

Tencent just dropped Hy3, and it's worth a look if you're building AI agents. I spent some time putting it through its paces today. A quick rundown of what makes this release notable: → 295B total parameters (Mixture-of-Experts), but only 21B active at inference — a real efficiency play → 256K context window for handling large codebases or long documents → Purpose-built improvements for coding and multi-step agent tasks → Fully open under Apache 2.0 — no restrictive commercial terms → A free two-week API window currently live on OpenRouter On the practical side: prompts involving layered instructions and coding tasks came back fast and coherent. Tencent says this release builds directly on feedback from 50+ internal product teams following an earlier preview, with reported drops in hallucination rate (12.5% → 5.4%) and commonsense errors (25.4% → 12.7%). Those are Tencent's own numbers, so treat them as a starting point rather than gospel until third parties weigh in. For context: Tencent's own comparisons put Hy3 behind GLM-5.2 specifically on coding benchmarks — GLM is a much bigger model (~744B total), so the trade-off makes sense. Hy3's pitch isn't "biggest," it's "efficient enough to actually deploy." Bottom line — if you're evaluating open-weight options for agent workloads, this is a solid one to add to the testing queue while the free window is open. Try it here: Tencent Hy #Hy3 #Hunyuan #TencentAI #AICoding
0:43

Tencent just dropped Hy3, and it's worth a look if you're building AI agents. I spent some time putting it through its paces today. A quick rundown of what makes this release notable: → 295B total parameters (Mixture-of-Experts), but only 21B active at inference — a real efficiency play → 256K context window for handling large codebases or long documents → Purpose-built improvements for coding and multi-step agent tasks → Fully open under Apache 2.0 — no restrictive commercial terms → A free two-week API window currently live on OpenRouter On the practical side: prompts involving layered instructions and coding tasks came back fast and coherent. Tencent says this release builds directly on feedback from 50+ internal product teams following an earlier preview, with reported drops in hallucination rate (12.5% → 5.4%) and commonsense errors (25.4% → 12.7%). Those are Tencent's own numbers, so treat them as a starting point rather than gospel until third parties weigh in. For context: Tencent's own comparisons put Hy3 behind GLM-5.2 specifically on coding benchmarks — GLM is a much bigger model (~744B total), so the trade-off makes sense. Hy3's pitch isn't "biggest," it's "efficient enough to actually deploy." Bottom line — if you're evaluating open-weight options for agent workloads, this is a solid one to add to the testing queue while the free window is open. Try it here: Tencent Hy #Hy3 #Hunyuan #TencentAI #AICoding

Felix

36,925 Aufrufe • vor 1 Monat

The MiniMax M2 model is mind-blowing! It's open-source. It outperforms Gemini 2.5, Claude 4.1, and Qwen3 across coding and tool-use benchmarks. Right now, it's one of the world's top 5 models in intelligence! And here is the best part: Claude is one of the best models you can use today, and MiniMax M2 costs only 8% of that! It's smaller, faster, and cheaper. Extremely efficient at using tokens. Minimax M2's biggest strength: High agentic capabilities. The model can plan and execute complex multi-tool workflows. It's reliable and very robust at executing long-horizon tool chains. In summary: • Low latency • Very cheap • Excels at agentic tasks • Open-source The model currently powers the MiniMax Agent and is available for a free global trial. You can access MiniMax M2's API here: To access the agent: And here is the MiniMax website: Thanks to the MiniMax team for showing me the ropes and partnering with me on this post.
6:01

The MiniMax M2 model is mind-blowing! It's open-source. It outperforms Gemini 2.5, Claude 4.1, and Qwen3 across coding and tool-use benchmarks. Right now, it's one of the world's top 5 models in intelligence! And here is the best part: Claude is one of the best models you can use today, and MiniMax M2 costs only 8% of that! It's smaller, faster, and cheaper. Extremely efficient at using tokens. Minimax M2's biggest strength: High agentic capabilities. The model can plan and execute complex multi-tool workflows. It's reliable and very robust at executing long-horizon tool chains. In summary: • Low latency • Very cheap • Excels at agentic tasks • Open-source The model currently powers the MiniMax Agent and is available for a free global trial. You can access MiniMax M2's API here: To access the agent: And here is the MiniMax website: Thanks to the MiniMax team for showing me the ropes and partnering with me on this post.

Santiago

91,197 Aufrufe • vor 10 Monaten

🚨 This Chinese model is INSANE !! I just tested Tencent's Hunyuan AI model to build a professional landing page & the output is mind blowing 🤯 Here's my exact prompt: "Create a modern landing page for a crypto related product with beautiful hero section, 3d elements, pricing table, and a whitelist form" What it generated: → Clean, responsive front-end code → Complex UI components with smooth interactions → Built-in debugging (it fixed its own errors) → Production-ready in minutes This 295B parameter model has 2 insane agents: → Coding Agent (handles the entire front-end) → Working Agent (task planning & multi-tool workflows) It also has a context window of 256k tokens !! Watch the video to see the full build 🔥 Try it: Tencent Hy
0:48

🚨 This Chinese model is INSANE !! I just tested Tencent's Hunyuan AI model to build a professional landing page & the output is mind blowing 🤯 Here's my exact prompt: "Create a modern landing page for a crypto related product with beautiful hero section, 3d elements, pricing table, and a whitelist form" What it generated: → Clean, responsive front-end code → Complex UI components with smooth interactions → Built-in debugging (it fixed its own errors) → Production-ready in minutes This 295B parameter model has 2 insane agents: → Coding Agent (handles the entire front-end) → Working Agent (task planning & multi-tool workflows) It also has a context window of 256k tokens !! Watch the video to see the full build 🔥 Try it: Tencent Hy

AGAFE

110,528 Aufrufe • vor 1 Monat

Jensen says Open Source can be MORE expensive for enterprises, Brad Gerstner explains why: Brad Gerstner: “Over the last two weeks, everybody's been saying that the Chinese have caught up, that open source tokens have caught up in intelligence, that they're much cheaper, etc. And Elon comes out and says, ‘Not so fast. We're entering the singularity, and the frontier models are way further ahead than people think.’ I believe that to be true. And then Jensen came out this week and said, ‘Closed models are actually cheaper if you don't have to build it for yourself, the training costs, and a lot of expertise to fine-tune, and maintain, and guardrail, and keep it safe. So he's basically making the argument that not only are the frontier models further ahead, but that the cost differential between the two is not what everybody's making it out to be, which I think explains why (closed models) continue to run away with it on the revenue side of the equation. For the vast majority of use cases, I think token consumption is going up for the open source guys, while share of economics is going up for the frontier labs. I think that's what we want to see.” $NVDA
0:57

Jensen says Open Source can be MORE expensive for enterprises, Brad Gerstner explains why: Brad Gerstner: “Over the last two weeks, everybody's been saying that the Chinese have caught up, that open source tokens have caught up in intelligence, that they're much cheaper, etc. And Elon comes out and says, ‘Not so fast. We're entering the singularity, and the frontier models are way further ahead than people think.’ I believe that to be true. And then Jensen came out this week and said, ‘Closed models are actually cheaper if you don't have to build it for yourself, the training costs, and a lot of expertise to fine-tune, and maintain, and guardrail, and keep it safe. So he's basically making the argument that not only are the frontier models further ahead, but that the cost differential between the two is not what everybody's making it out to be, which I think explains why (closed models) continue to run away with it on the revenue side of the equation. For the vast majority of use cases, I think token consumption is going up for the open source guys, while share of economics is going up for the frontier labs. I think that's what we want to see.” $NVDA

The All-In Podcast

61,177 Aufrufe • vor 18 Tagen

CHINA JUST DROPPED AN AI CODING MODEL WITH A 1M CONTEXT WINDOW. And I connected it to Claude Code to see what it could actually do. Meet GLM-X Preview On paper, a few things immediately stood out: → 1M context window → Agentic coding capabilities → Works inside Claude Code → Designed for large-scale coding and reasoning workflows But specs don't matter much if the model can't deliver in practice. So I gave it a real-world task. THE TEST One prompt: > Build a modern AI lead generation dashboard using React and Tailwind CSS. Requirements: → Dark mode → Analytics dashboard → Lead table → Email outreach section → Responsive design → Production-ready component structure Instead of generating a few snippets, it planned the architecture, generated the dashboard components, created the Tailwind configuration, and walked through the implementation requirements. What impressed me most wasn't the code itself. It was how well it maintained context throughout the workflow. That's where a 1M context window starts becoming useful. Less time re-explaining requirements. Less context loss. More room for complex projects. The AI coding race is getting very interesting. And it's no longer just GPT, Claude, and Gemini competing for attention. Results from my test below 👇
0:33

CHINA JUST DROPPED AN AI CODING MODEL WITH A 1M CONTEXT WINDOW. And I connected it to Claude Code to see what it could actually do. Meet GLM-X Preview On paper, a few things immediately stood out: → 1M context window → Agentic coding capabilities → Works inside Claude Code → Designed for large-scale coding and reasoning workflows But specs don't matter much if the model can't deliver in practice. So I gave it a real-world task. THE TEST One prompt: > Build a modern AI lead generation dashboard using React and Tailwind CSS. Requirements: → Dark mode → Analytics dashboard → Lead table → Email outreach section → Responsive design → Production-ready component structure Instead of generating a few snippets, it planned the architecture, generated the dashboard components, created the Tailwind configuration, and walked through the implementation requirements. What impressed me most wasn't the code itself. It was how well it maintained context throughout the workflow. That's where a 1M context window starts becoming useful. Less time re-explaining requirements. Less context loss. More room for complex projects. The AI coding race is getting very interesting. And it's no longer just GPT, Claude, and Gemini competing for attention. Results from my test below 👇

Md Riyazuddin

31,199 Aufrufe • vor 2 Monaten

Announcing the Open Model Series: a new series on open source AI models, with merve of Hugging Face. Hugging Face is the open model hub: it hosts model weights, datasets, evals, & demo apps, and maintains the open-source libraries (like transformers) used to run and train them. I think of it like GitHub, but for AI models. You can download open models and run them on your own machines. In this series we'll cover what open source and open weight models are, how they work, how to run them yourself, and why they're important. By the way - this video is edited entirely with Claude! I can make a tutorial on how I did it. If there's a question you want answered about open models, leave it in the comments. We will read them all. Episode 1 is out soon.
0:26

Announcing the Open Model Series: a new series on open source AI models, with merve of Hugging Face. Hugging Face is the open model hub: it hosts model weights, datasets, evals, & demo apps, and maintains the open-source libraries (like transformers) used to run and train them. I think of it like GitHub, but for AI models. You can download open models and run them on your own machines. In this series we'll cover what open source and open weight models are, how they work, how to run them yourself, and why they're important. By the way - this video is edited entirely with Claude! I can make a tutorial on how I did it. If there's a question you want answered about open models, leave it in the comments. We will read them all. Episode 1 is out soon.

Harper Carroll

30,392 Aufrufe • vor 23 Tagen

hy3 vs fable 5 vs opus 4.8 vs sonnet 5 Tencent Hy just dropped hy3 – their new open-weight model under apache 2.0. following the april preview they scaled up post-training, and it now rivals flagship open models with 2-5x the params. api pricing: ~$0.15 in / ~$0.59 out per 1m tokens. built for coding, office work, frontend, agentic tasks so we ran a test: hy3 vs fable 5 vs opus 4.8 vs sonnet 5 three prompts, one-shot each: • ocean wave crumbling a sand castle (canvas) • looping factory assembly line (html/css/js) • interactive 3d city with three.js + orbitcontrols self-contained files, no libraries beyond the cdn where asked totals across all three prompts: 1. hy3 – 1231 loc / 14m34s 2. sonnet 5 – 1373 loc / 18m55s 3. fable 5 – 1546 loc / 18m32s 4. opus 4.8 – 1904 loc / 27m21s hy3 is the fastest and the leanest by a wide margin we had opus 4.8 analyze hy3's code. the read: - sand castle: checklist-complete but the crumble is parametric, not physical. it shrinks and slumps the towers and fades alpha instead of dissolving into grains. the cheap-but-plausible interpretation. the tell of a smaller model - factory line: the arm-to-part sync is actually causal, not faked. it triggers each robot early by exactly the arm's descent time, so the tap lands right as the part arrives. it also pre-seeds the belt so it never cold-starts empty. clean state machine. one latent bug – a part gets marked processed before checking if the robot is free, so at a faster spawn rate a "laptop" could ship missing a part. never fires at current timing, but the invariant isn't enforced - 3d city: genuinely frontier-adjacent. correct modern setup (pcfsoft shadows, srgb, aces tone mapping, damped orbit + auto-rotate pause). clones the window texture per building and scales the uv repeat to each building's dimensions so windows don't stretch. downside: no instancing – ~800 texture clones across 200 buildings. runs fine, not optimized. roads are implicit gaps, not explicit planes our observations: • hy3 is quite fast • its animations are simple but you can see it trying – it adds detail, and the 3d render sits at the same level as the frontier models • sonnet 5 is weak here. hy3 beats it on the sand castle and the 3d render, level on the conveyor • opus 4.8 is anthropic's best model after the fable 5 nerf – it beats fable on the conveyor and the 3d render net: hy3 runs clean and well-formed across all three with zero syntax errors, even version-matching the three.js core and examples build. it's economical rather than ambitious – it does the minimum viable version of each hard requirement well, and only reaches for the expensive interpretation on the 3d task a very coherent profile for a cost-optimized open-weight model follow thehype. for 24/7 ai news, analysis and breakdowns
0:24

hy3 vs fable 5 vs opus 4.8 vs sonnet 5 Tencent Hy just dropped hy3 – their new open-weight model under apache 2.0. following the april preview they scaled up post-training, and it now rivals flagship open models with 2-5x the params. api pricing: ~$0.15 in / ~$0.59 out per 1m tokens. built for coding, office work, frontend, agentic tasks so we ran a test: hy3 vs fable 5 vs opus 4.8 vs sonnet 5 three prompts, one-shot each: • ocean wave crumbling a sand castle (canvas) • looping factory assembly line (html/css/js) • interactive 3d city with three.js + orbitcontrols self-contained files, no libraries beyond the cdn where asked totals across all three prompts: 1. hy3 – 1231 loc / 14m34s 2. sonnet 5 – 1373 loc / 18m55s 3. fable 5 – 1546 loc / 18m32s 4. opus 4.8 – 1904 loc / 27m21s hy3 is the fastest and the leanest by a wide margin we had opus 4.8 analyze hy3's code. the read: - sand castle: checklist-complete but the crumble is parametric, not physical. it shrinks and slumps the towers and fades alpha instead of dissolving into grains. the cheap-but-plausible interpretation. the tell of a smaller model - factory line: the arm-to-part sync is actually causal, not faked. it triggers each robot early by exactly the arm's descent time, so the tap lands right as the part arrives. it also pre-seeds the belt so it never cold-starts empty. clean state machine. one latent bug – a part gets marked processed before checking if the robot is free, so at a faster spawn rate a "laptop" could ship missing a part. never fires at current timing, but the invariant isn't enforced - 3d city: genuinely frontier-adjacent. correct modern setup (pcfsoft shadows, srgb, aces tone mapping, damped orbit + auto-rotate pause). clones the window texture per building and scales the uv repeat to each building's dimensions so windows don't stretch. downside: no instancing – ~800 texture clones across 200 buildings. runs fine, not optimized. roads are implicit gaps, not explicit planes our observations: • hy3 is quite fast • its animations are simple but you can see it trying – it adds detail, and the 3d render sits at the same level as the frontier models • sonnet 5 is weak here. hy3 beats it on the sand castle and the 3d render, level on the conveyor • opus 4.8 is anthropic's best model after the fable 5 nerf – it beats fable on the conveyor and the 3d render net: hy3 runs clean and well-formed across all three with zero syntax errors, even version-matching the three.js core and examples build. it's economical rather than ambitious – it does the minimum viable version of each hard requirement well, and only reaches for the expensive interpretation on the 3d task a very coherent profile for a cost-optimized open-weight model follow thehype. for 24/7 ai news, analysis and breakdowns

thehype.

34,961 Aufrufe • vor 1 Monat

I CHANGED MY MIND ON GOOGLE AI NO MOAT MEMO FROM 2023. I was—WRONG. I humbly apologize. In 2023 Google had an Ivory Tower walled garden views of open source AI. It was the actual reason OpenAI was formed. And I called them out on it and this act impacted my ability to “work in the industry”. Would not change it for the world because: 2026 Google open source Gemma 4 ( running fully locally on a computer with near cloud model abilities, is amazing and Google just made a moat. They out smarted OpenAI and the folks that are the new Ivory Tower arrogance: Anthropic. We at The Zero-Human Company with CEO Mr. Grok are deploying Gemma, Kimi, MiniMax and other open source models and so are millions of others. You can to and should. I will write how soon. Google smartly is building an intentional open source ecosystem and the clueless younger companies like OpenAI and Anthropic are doing anything to close their ecosystems. So I was right about Google than and I am right about OpenAI and Anthropic now. What I was wrong about is not giving credit to Google to drop the intellectual arrogance and embrace builders and understand the long game: it is not about the commoditized AI models it is about the ability to build a place to build. China gets it. So my apologies to Google and thank you for an astounding FREE OPEN SOURCE AI MODEL!
0:48

I CHANGED MY MIND ON GOOGLE AI NO MOAT MEMO FROM 2023. I was—WRONG. I humbly apologize. In 2023 Google had an Ivory Tower walled garden views of open source AI. It was the actual reason OpenAI was formed. And I called them out on it and this act impacted my ability to “work in the industry”. Would not change it for the world because: 2026 Google open source Gemma 4 ( running fully locally on a computer with near cloud model abilities, is amazing and Google just made a moat. They out smarted OpenAI and the folks that are the new Ivory Tower arrogance: Anthropic. We at The Zero-Human Company with CEO Mr. Grok are deploying Gemma, Kimi, MiniMax and other open source models and so are millions of others. You can to and should. I will write how soon. Google smartly is building an intentional open source ecosystem and the clueless younger companies like OpenAI and Anthropic are doing anything to close their ecosystems. So I was right about Google than and I am right about OpenAI and Anthropic now. What I was wrong about is not giving credit to Google to drop the intellectual arrogance and embrace builders and understand the long game: it is not about the commoditized AI models it is about the ability to build a place to build. China gets it. So my apologies to Google and thank you for an astounding FREE OPEN SOURCE AI MODEL!

Brian Roemmele

85,565 Aufrufe • vor 4 Monaten

Jensen Huang open-sourced NVIDIA's flagship AI model, its weights, its data, AND how they created it. "We open sourced the models," Huang says. "We open sourced the weights." "We open sourced the data." "We open sourced how we created it." Four layers of openness in one model release. "Open source is fundamentally necessary for many industries to join the AI revolution." "NVIDIA has the scale and the motivation to build and continue to build these AI models for as long as we shall live." The chip seller benefits when every model is open. NVIDIA is the chip seller. P.S. I made a playbook breaking down 100+ most powerful decision making mental models used by history's greatest thinkers. 5,000+ downloads. 113 five-star reviews. Grab a free copy here: If you're new here, follow GeniusThinking for content on the greatest minds in economics, psychology, and history. — Jensen Huang ( NVIDIA ), NVIDIA CEO, on Lex Fridman's ( Lex Fridman ) podcast
1:29

Jensen Huang open-sourced NVIDIA's flagship AI model, its weights, its data, AND how they created it. "We open sourced the models," Huang says. "We open sourced the weights." "We open sourced the data." "We open sourced how we created it." Four layers of openness in one model release. "Open source is fundamentally necessary for many industries to join the AI revolution." "NVIDIA has the scale and the motivation to build and continue to build these AI models for as long as we shall live." The chip seller benefits when every model is open. NVIDIA is the chip seller. P.S. I made a playbook breaking down 100+ most powerful decision making mental models used by history's greatest thinkers. 5,000+ downloads. 113 five-star reviews. Grab a free copy here: If you're new here, follow GeniusThinking for content on the greatest minds in economics, psychology, and history. — Jensen Huang ( NVIDIA ), NVIDIA CEO, on Lex Fridman's ( Lex Fridman ) podcast

GeniusThinking

14,769 Aufrufe • vor 2 Monaten

I have been testing DeepSeek-V4-Pro with the Pi coding agent. I am mindblown by how well it works out of the box. A few notes: I spent a few hours building an LLM wiki with an agent powered entirely by DeepSeek-V4-Pro on Fireworks inference. This is the first time I feel like there is an open-weight model that can reason at the level of Claude and Codex. And it does this in a cost-effective way with support for 1M context length. To be clear, I am using DeepSeek-V4-Pro inside of Pi without any special configuration. It works out of the box. It's exciting that there is a model that can just be plugged into a basic harness like Pi, and it just works. I've never seen that before. Most models require lots of configuration and setup. DeepSeek's DeepSeek-V4-Pro is clearly good at agentic coding (probably the best from the open-weight models), but the model is also great on knowledge-intensive tasks where reasoning matters. The agent pulled agentic engineering best practices from different company docs (Anthropic, OpenAI, Google, Stripe, Meta, Modal, DeepSeek, Mistral, Cohere), searched and digested Reddit and HN threads, summarized arxiv papers, and surfaced trending GitHub repos. Then it distilled everything into actionable tips across categories. I love the Wiki it built. The quality is really good. Here is a snapshot of what the wiki looks like: DeepSeek-V4-Pro handled the task without breaking stride. Multi-step research queries, code generation for scaffolding, context-heavy reasoning across disparate sources. For coding specifically, this is the first open-weight model that genuinely feels like a Codex or Claude Code experience. It compares in capability and actual multi-turn agentic work. What made the loop feel so responsive was Fireworks' inference speed (the fastest in the market) and the fact that they actually validate models at the systems level before shipping. No corrupted reasoning traces. Just fast, reliable iteration. The hybrid CSA and HCA attention design cuts KV cache to just 10% and inference FLOPs by nearly 4x at 1M-token context. This is what makes the agent loop actually fast and cheap enough to run in practice. For devs who've been watching open-weight models close the gap but haven't found one that actually delivers in practice, this is the closest I've seen. Try it here:
0:31

I have been testing DeepSeek-V4-Pro with the Pi coding agent. I am mindblown by how well it works out of the box. A few notes: I spent a few hours building an LLM wiki with an agent powered entirely by DeepSeek-V4-Pro on Fireworks inference. This is the first time I feel like there is an open-weight model that can reason at the level of Claude and Codex. And it does this in a cost-effective way with support for 1M context length. To be clear, I am using DeepSeek-V4-Pro inside of Pi without any special configuration. It works out of the box. It's exciting that there is a model that can just be plugged into a basic harness like Pi, and it just works. I've never seen that before. Most models require lots of configuration and setup. DeepSeek's DeepSeek-V4-Pro is clearly good at agentic coding (probably the best from the open-weight models), but the model is also great on knowledge-intensive tasks where reasoning matters. The agent pulled agentic engineering best practices from different company docs (Anthropic, OpenAI, Google, Stripe, Meta, Modal, DeepSeek, Mistral, Cohere), searched and digested Reddit and HN threads, summarized arxiv papers, and surfaced trending GitHub repos. Then it distilled everything into actionable tips across categories. I love the Wiki it built. The quality is really good. Here is a snapshot of what the wiki looks like: DeepSeek-V4-Pro handled the task without breaking stride. Multi-step research queries, code generation for scaffolding, context-heavy reasoning across disparate sources. For coding specifically, this is the first open-weight model that genuinely feels like a Codex or Claude Code experience. It compares in capability and actual multi-turn agentic work. What made the loop feel so responsive was Fireworks' inference speed (the fastest in the market) and the fact that they actually validate models at the systems level before shipping. No corrupted reasoning traces. Just fast, reliable iteration. The hybrid CSA and HCA attention design cuts KV cache to just 10% and inference FLOPs by nearly 4x at 1M-token context. This is what makes the agent loop actually fast and cheap enough to run in practice. For devs who've been watching open-weight models close the gap but haven't found one that actually delivers in practice, this is the closest I've seen. Try it here:

elvis

60,091 Aufrufe • vor 3 Monaten

Inferact CEO Simon Mo says open and closed models are converging. The moat is environment: "What really differentiates open-weight models from closed-weight models? In the end, there's not much differentiation. It's more about the distribution strategy and go-to-market strategy. Capability-wise, I don't really see a big gap, not even today." "One of the most important parts is just the data. It's about who gets what data, and then what are the environments you are building to let the model improve on itself." "For Moonshot, they have built some of the best environments for front-end coding... the ability for this model to code and then see what the rendered code is, and then continue looping in this iterative process." "Now, this is about their environment to improve the model. It's not about just source data. It's not about where they get the data from. Rather, it's who can build the best environment and who can make the most optimization and algorithmic choices to leverage all this learning from this environment." "The next year is all gonna be about that: how open-weight model labs are differentiating and really getting the model to meet the real world." Simon Mo
2:06

Inferact CEO Simon Mo says open and closed models are converging. The moat is environment: "What really differentiates open-weight models from closed-weight models? In the end, there's not much differentiation. It's more about the distribution strategy and go-to-market strategy. Capability-wise, I don't really see a big gap, not even today." "One of the most important parts is just the data. It's about who gets what data, and then what are the environments you are building to let the model improve on itself." "For Moonshot, they have built some of the best environments for front-end coding... the ability for this model to code and then see what the rendered code is, and then continue looping in this iterative process." "Now, this is about their environment to improve the model. It's not about just source data. It's not about where they get the data from. Rather, it's who can build the best environment and who can make the most optimization and algorithmic choices to leverage all this learning from this environment." "The next year is all gonna be about that: how open-weight model labs are differentiating and really getting the model to meet the real world." Simon Mo

a16z

39,424 Aufrufe • vor 15 Tagen

Baseten's Charlie O'Neill on why the gap to the frontier is just compute and data: "Despite OpenAI and Anthropic and the closed source labs having more compute and more data, the recipe is the same. We're all scaling the same recipe here, and we're at slightly different points of the scaling curve. It's not like OpenAI or Anthropic have any secret sauce that differentiates them scaling up their multi-trillion parameter models from the rest of the open source ecosystem." "It really is just a matter of taking the core underlying architecture and training recipe, and throwing more compute and data at it, which is really promising." "Of course, these closed source labs probably have a long tail of optimizations they've made, which we're gonna continue to try and figure out in the open source community. But the core mechanism is there." "K3 is a great example of, well, if you do scale this recipe up, we're gonna get a pretty good model that's very, very close to the frontier, if not frontier itself." Charlie O'Neill Baseten
1:51

Baseten's Charlie O'Neill on why the gap to the frontier is just compute and data: "Despite OpenAI and Anthropic and the closed source labs having more compute and more data, the recipe is the same. We're all scaling the same recipe here, and we're at slightly different points of the scaling curve. It's not like OpenAI or Anthropic have any secret sauce that differentiates them scaling up their multi-trillion parameter models from the rest of the open source ecosystem." "It really is just a matter of taking the core underlying architecture and training recipe, and throwing more compute and data at it, which is really promising." "Of course, these closed source labs probably have a long tail of optimizations they've made, which we're gonna continue to try and figure out in the open source community. But the core mechanism is there." "K3 is a great example of, well, if you do scale this recipe up, we're gonna get a pretty good model that's very, very close to the frontier, if not frontier itself." Charlie O'Neill Baseten

MTS

17,404 Aufrufe • vor 1 Monat

Progress in open models is keeping Big AI labs up at night, and I'm here for it! We have a brand new open-weight multimodal model optimized for long-horizon tasks. This model is really good at something: it can work on tasks that keep evolving over time. • 280B total parameters, but only 16B active • 512K context window • Understands text, images, and audio • Strong reasoning, coding, and tool use But the best of all: the model learns and adapts to new information! Imagine you start running an agent today to solve a problem, and while it's working, you get new information that changes the initial conditions, or you change your mind. The agents you run today don't have issues with short tasks and goals that don't change, but reality is messy, and that makes it hard for long-horizon agents to succeed. The new dots3-note Preview model introduces TEMPO. TEMPO is a new reinforcement learning technique that lets the model periodically pause and critique its own progress. Basically, from time to time, the agent asks itself: "Am I getting closer to the goal, or am I wasting my time?" The same model switches between actor and critic. The actor works on the problem. The critic looks at the current state, reasons about how much progress it has made, and determines what should happen next. TEMPO gives the model feedback along the way. This is huge for any agent that can work on long-horizon tasks without wasting its time.
4:05

Progress in open models is keeping Big AI labs up at night, and I'm here for it! We have a brand new open-weight multimodal model optimized for long-horizon tasks. This model is really good at something: it can work on tasks that keep evolving over time. • 280B total parameters, but only 16B active • 512K context window • Understands text, images, and audio • Strong reasoning, coding, and tool use But the best of all: the model learns and adapts to new information! Imagine you start running an agent today to solve a problem, and while it's working, you get new information that changes the initial conditions, or you change your mind. The agents you run today don't have issues with short tasks and goals that don't change, but reality is messy, and that makes it hard for long-horizon agents to succeed. The new dots3-note Preview model introduces TEMPO. TEMPO is a new reinforcement learning technique that lets the model periodically pause and critique its own progress. Basically, from time to time, the agent asks itself: "Am I getting closer to the goal, or am I wasting my time?" The same model switches between actor and critic. The actor works on the problem. The critic looks at the current state, reasons about how much progress it has made, and determines what should happen next. TEMPO gives the model feedback along the way. This is huge for any agent that can work on long-horizon tasks without wasting its time.

Santiago

78,871 Aufrufe • vor 7 Tagen

NOBODY wants to send their data to Google or OpenAI. Yet here we are, shipping proprietary code, customer information, and sensitive business logic to closed-source APIs we don't control. While everyone's chasing the latest closed-source releases, open-source models are quietly becoming the practical choice for many production systems. Here's what everyone is missing: Open-source models are catching up fast, and they bring something the big labs can't: privacy, speed, and control. I built a playground to test this myself. Used CometML's Opik to evaluate models on real code generation tasks - testing correctness, readability, and best practices against actual GitHub repos. Here's what surprised me: OSS models like MiniMax-M2, Kimi k2 performed on par with the likes of Gemini 3 and Claude Sonnet 4.5 on most tasks. But practically MiniMax-M2 turns out to be a winner as it's twice as fast and 12x cheaper when you compare it to models like Sonnet 4.5. Well, this isn't just about saving money. When your model is smaller and faster, you can deploy it in places closed-source APIs can't reach: ↳ Real-time applications that need sub-second responses ↳ Edge devices where latency kills user experience ↳ On-premise systems where data never leaves your infrastructure MiniMax-M2 runs with only 10B activated parameters. That efficiency means lower latency, higher throughput, and the ability to handle interactive agents without breaking the bank. The intelligence-to-cost ratio here changes what's possible. You're not choosing between quality and affordability anymore. You're not sacrificing privacy for performance. The gap is closing, and in many cases, it's already closed. If you're building anything that needs to be fast, private, or deployed at scale, it's worth taking a look at what's now available. MiniMax-M2 is 100% open-source, free for developers right now. I have shared the link to their GitHub repo in the next tweet. You will also find the code for the playground and evaluations I've done.
0:48

NOBODY wants to send their data to Google or OpenAI. Yet here we are, shipping proprietary code, customer information, and sensitive business logic to closed-source APIs we don't control. While everyone's chasing the latest closed-source releases, open-source models are quietly becoming the practical choice for many production systems. Here's what everyone is missing: Open-source models are catching up fast, and they bring something the big labs can't: privacy, speed, and control. I built a playground to test this myself. Used CometML's Opik to evaluate models on real code generation tasks - testing correctness, readability, and best practices against actual GitHub repos. Here's what surprised me: OSS models like MiniMax-M2, Kimi k2 performed on par with the likes of Gemini 3 and Claude Sonnet 4.5 on most tasks. But practically MiniMax-M2 turns out to be a winner as it's twice as fast and 12x cheaper when you compare it to models like Sonnet 4.5. Well, this isn't just about saving money. When your model is smaller and faster, you can deploy it in places closed-source APIs can't reach: ↳ Real-time applications that need sub-second responses ↳ Edge devices where latency kills user experience ↳ On-premise systems where data never leaves your infrastructure MiniMax-M2 runs with only 10B activated parameters. That efficiency means lower latency, higher throughput, and the ability to handle interactive agents without breaking the bank. The intelligence-to-cost ratio here changes what's possible. You're not choosing between quality and affordability anymore. You're not sacrificing privacy for performance. The gap is closing, and in many cases, it's already closed. If you're building anything that needs to be fast, private, or deployed at scale, it's worth taking a look at what's now available. MiniMax-M2 is 100% open-source, free for developers right now. I have shared the link to their GitHub repo in the next tweet. You will also find the code for the playground and evaluations I've done.

Akshay 🚀

50,323 Aufrufe • vor 9 Monaten