WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-02-17 1 00:00:00.000 --> 00:00:08.564 Good morning and welcome to the Builder's Briefing for February seventeenth, twenty twenty-six. I'm Alex, and with me as always is Sam. We've got a packed one today — a big open-weight agent model drop from Alibaba, some spicy drama around AI censorship and transparency, and the agent tooling ecosystem just keeps getting thicker. 2 00:00:08.564 --> 00:00:12.057 Yeah, today really feels like an inflection point for the agentic AI space. Lots of puzzle pieces clicking together. Let's get into it. 3 00:00:12.057 --> 00:00:21.293 Alright, the big story — Alibaba's Qwen team dropped Qwen three-point-five, and they're positioning it explicitly as a native multimodal agent model. And the key word there is native. This isn't a chat model with vision bolted on as an afterthought — the architecture is built from the ground up to reason across text, images, and tool use in a single pass. 4 00:00:21.293 --> 00:00:29.546 That's a really important distinction. Because right now, if you're building agent workflows, you're typically chaining a vision model into a text model into a tool-use layer, and every hop adds latency and failure modes. A single model that handles the full loop? That's a fundamentally different developer experience. 5 00:00:29.546 --> 00:00:35.213 Exactly. And because it's open-weight, you can self-host it, fine-tune it, and avoid those per-token API costs — which, if you've ever run an agent loop that does like forty tool calls, you know those costs add up fast. 6 00:00:35.213 --> 00:00:43.595 Right, and what's wild is the timing. Between Qwen three-point-five, Mistral's agent work, and everything else in the open-weight ecosystem, builders now have real leverage. You can go to your API provider and negotiate, or just go self-hosted. The agent model race is genuinely fragmenting away from the pure API providers. 7 00:00:43.595 --> 00:00:52.288 The HN thread had over two hundred sixty points and active discussion. Early reports suggest strong performance on interleaved image-text reasoning and function calling. If you're building anything with multi-step tool use — especially involving visual inputs — benchmark this against your current stack this week. Link in the briefing. 8 00:00:52.288 --> 00:00:57.877 Okay, moving into AI and models news. There's a project called Heretic trending hard on GitHub — over forty-two hundred stars. It's an open-source tool that automatically removes safety refusals from language models. 9 00:00:57.877 --> 00:01:06.337 Yeah, this one's going to be polarizing. If you're running local models for internal tooling and you're hitting refusal walls on totally benign tasks — like generating security test cases or medical documentation — I get the frustration. But shipping this in production? You'd better have a very clear policy and hosting story. 10 00:01:06.337 --> 00:01:12.598 A hundred percent. On the other side of the Anthropic coin, there's some developer backlash brewing. Apparently Anthropic has been making it harder to distinguish AI-generated content from human content, and developers are not happy about it. 11 00:01:12.598 --> 00:01:17.928 That's interesting because trust and transparency in AI outputs is quickly becoming a product differentiator, not just an ethics checkbox. If you're building on Claude's API, this is worth watching closely. 12 00:01:17.928 --> 00:01:26.854 And speaking of Claude — two great resources dropped. There's an awesome-claude-code community list curating hooks, skills, and agent orchestrators, now at over seven hundred stars. And Anthropic's own claude-quickstarts repo is trending for fast API bootstrapping. If you're a daily Claude Code user, these are goldmines. Links in the briefing. 13 00:01:26.854 --> 00:01:33.633 Oh, and one observation I loved that was gaining traction — Claude Code apparently works significantly better on clean codebases. Good naming, clear module boundaries, solid READMEs. It amplifies existing code quality rather than compensating for poor structure. 14 00:01:33.633 --> 00:01:38.626 Which means your investment in code hygiene now has a direct multiplier effect on AI output quality. That's a pretty compelling argument for finally doing that refactor you've been putting off. 15 00:01:38.626 --> 00:01:44.628 Ha, exactly. Also, quick one — ICML is embedding hidden prompts in conference papers to catch AI-generated reviews. Only LLMs follow the trap instructions, so they get flagged automatically. Expect that pattern to spread everywhere. 16 00:01:44.628 --> 00:01:50.398 Clever and terrifying. Alright, developer tools. There's a great Show HN project called MicroGPT — it lets you visualize a working GPT in your browser, step by step. Watch attention, watch token generation, the whole thing. 17 00:01:50.398 --> 00:01:55.909 Oh, that's perfect for anyone who needs to explain transformers to stakeholders or students. I've bookmarked that one immediately. Way better than waving your hands and saying 'it's like autocomplete but smarter.' 18 00:01:55.909 --> 00:02:02.067 Ha! And there's a fun one — someone gave Claude direct access to a pen plotter and documented the results. The failure modes and iteration patterns are genuinely instructive if you're thinking about any kind of LLM-to-hardware agent loop. 19 00:02:02.067 --> 00:02:07.370 That's the kind of experiment I love. Real-world physical agents are so different from software agents. The feedback loops are slower, the errors are messier, and you can't just retry without consequences. 20 00:02:07.370 --> 00:02:15.650 Also worth flagging — there's an essay making the rounds about the 'Sideprocalypse,' the wave of low-effort AI-generated side projects flooding the internet. The bar for standing out just went up. Thoughtful design and solving real user problems matters more than ever when anyone can generate a landing page in minutes. 21 00:02:15.650 --> 00:02:18.935 Yep, the era of 'I built this in a weekend with AI' being impressive is over. Now it's 'okay, but does anyone actually use it?' 22 00:02:18.935 --> 00:02:23.411 Quick dip into startups and infrastructure. Ricursive Intelligence raised three hundred thirty-five million dollars at a four billion dollar valuation — in just four months. 23 00:02:23.411 --> 00:02:28.845 Four months to a four billion valuation. The AI fundraising environment is still just zero gravity. But the signal is clear — capital is flowing to teams and founder reputation, not necessarily to products yet. 24 00:02:28.845 --> 00:02:35.494 And on the hardware side, AMD deployed their Helios AI architecture with MI four-fifty-five X GPUs in India through TCS. The ROCm ecosystem keeps maturing, and if you're evaluating non-NVIDIA options for inference workloads, enterprise adoption is now real. 25 00:02:35.494 --> 00:02:46.955 Quick hits — Hummingbot, open-source high-frequency crypto trading bots, trending at about fifteen hundred stars. Someone built a homebrew laptop on the sixty-five-oh-two processor, which is just delightful. Real-time path tracing with global illumination running in WebGL. And Apple announced a March fourth event — new MacBook, iPad, and iPhone expected, so if you're shipping Apple platform apps, start testing against the latest betas now. 26 00:02:46.955 --> 00:02:50.396 Oh, and the Apple event also had Face ID smart doorbell rumors, so HomeKit developers should keep an eye out for new smart home APIs. 27 00:02:50.396 --> 00:02:59.167 So stepping back — the big takeaway this week is that the agent model layer is splitting wide open. Qwen three-point-five gives you a self-hostable native multimodal agent model. Google Stitch got its Hatter agent for design workflows with MCP export. Claude Code's ecosystem is maturing with community extensions and official quickstarts. 28 00:02:59.167 --> 00:03:07.239 If you're building agentic products, this really is the week to benchmark Qwen three-point-five against your current provider — especially if your agent loops involve vision or high token volumes. The cost and control advantages of open-weight agent models are getting too big to ignore for production workloads. 29 00:03:07.239 --> 00:03:10.939 That's the briefing for February seventeenth. All links and resources are in the show notes. Thanks for listening, and we'll see you next time. 30 00:03:10.939 --> 00:03:12.000 Go benchmark something. See you tomorrow!