WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-04-03 1 00:00:00.000 --> 00:00:08.341 Good morning and welcome to Builder's Briefing for April third, twenty twenty-six. I'm Alex, joined as always by Sam, and folks — this week is stacked. Two major open model drops, a wave of agent tooling, some security stories that'll make you audit your code, and Artemis Two is literally beaming 4K from the moon. 2 00:00:08.341 --> 00:00:12.101 Yeah, it's one of those weeks where you open your feed and just go, okay, I guess I'm not getting anything else done today. Let's get into it. 3 00:00:12.101 --> 00:00:19.092 So the big story — two massive open model releases within forty-eight hours of each other. Google dropped Gemma 4, the next generation of their open-weight family, and Alibaba's Qwen team shipped Qwen 3.6-Plus with an explicit tagline: 'towards real world agents.' 4 00:00:19.092 --> 00:00:25.738 That's interesting because both teams are basically saying the same thing at the same time. It's not about chat benchmarks anymore. It's about tool use, multi-step planning, long-context reliability — the stuff you actually need for agentic workflows. 5 00:00:25.738 --> 00:00:35.642 Exactly. And Gemma 4 is self-hostable, fine-tunable, no API lock-in. If it follows the Gemma 3 trajectory, the smaller variants are going to punch way above their weight on performance-per-parameter. Meanwhile Qwen 3.6-Plus is explicitly optimized for agent pipelines, so if you're building autonomous systems, benchmark it against Claude and GPT on your actual task chains. 6 00:00:35.642 --> 00:00:42.394 Right, and what's wild is AMD also launched their Lemonade server this same week — local inference on GPU plus NPU with an OpenAI-compatible API. So you can actually test these open models locally without any cloud spend. The timing is almost too perfect. 7 00:00:42.394 --> 00:00:48.431 The pattern is unmistakable. Open models are converging on agent-grade reliability, and the message for builders is clear: design for model-agnostic orchestration now, because your switching costs are about to drop dramatically. 8 00:00:48.431 --> 00:00:50.047 Don't marry the model, marry the orchestration layer. Got it. 9 00:00:50.047 --> 00:00:55.634 Okay, staying in the AI world — there's a repo that now publishes extracted system prompts from basically every major model. GPT 5.4, Claude Opus 4.6, Gemini 3.1 Pro, Grok 4.2, all of them. Link in the briefing. 10 00:00:55.634 --> 00:01:02.995 This is honestly the best free masterclass in prompt architecture. Studying how the providers themselves instruct their own models? That's the real cheat code. Also, a great reminder — never put secrets in your system prompts, because clearly they're not as secret as you think. 11 00:01:02.995 --> 00:01:10.780 Related to that, there's a detailed analysis of Claude Code's leaked system prompt and internal architecture. It shows exactly how Anthropic structures tool use, safety rails, and context management. If you're building on Claude Code, you should understand the guardrails you're working within. 12 00:01:10.780 --> 00:01:13.349 And the ones you can push on. Yeah, that's a must-read for anyone doing serious Claude Code work. 13 00:01:13.349 --> 00:01:15.520 One more on the AI side — r/programming has temporarily banned all LLM discussion. 14 00:01:15.520 --> 00:01:23.067 Okay, that's a vibe check on the whole industry right there. Community fatigue is real, but for builders the signal is just: find your audience where AI-assisted development is already the default. Don't waste energy debating legitimacy in spaces that have already made up their minds. 15 00:01:23.067 --> 00:01:30.005 Alright, developer tools — and there's a lot. The biggest GitHub engagement this week, over fourteen thousand stars, is OmX — think oh-my-zsh but for your coding agent. It adds plugin hooks, multi-agent coordination, and heads-up displays on top of OpenAI Codex. 16 00:01:30.005 --> 00:01:36.254 So it turns Codex from a solo tool into an orchestrated team. That's exactly the kind of tooling that makes sense when you look at where everything is heading. You're not going to have one agent doing everything — you need coordination. 17 00:01:36.254 --> 00:01:42.927 And Google shipped ADK-Go — their official Go toolkit for building, evaluating, and deploying AI agents. Code-first, not YAML-first. If your backend is Go and you've been jealous of Python's agent framework ecosystem, Google just met you where you are. 18 00:01:42.927 --> 00:01:51.162 About time, honestly. The Go community has been underserved on this front. I also want to shout out Rivet Actors — actor-model primitives specifically for stateful agents. If you need agents that maintain state across sessions, it's lower-level and more composable than full frameworks. Really elegant approach. 19 00:01:51.162 --> 00:01:55.769 And one fun one — Git Bayesect. Standard git bisect assumes deterministic pass-fail, right? This uses Bayesian inference to handle flaky tests and non-deterministic failures. 20 00:01:55.769 --> 00:01:58.497 Okay, whose CI doesn't have flaky tests? This is the bisect upgrade nobody knew they needed. I love it. 21 00:01:58.497 --> 00:02:04.852 Security corner. LinkedIn is being accused of illegally scanning your computer. BrowserGate.eu alleges unauthorized local system scanning, and this hit over eleven hundred points on Hacker News, so developers are very much paying attention. 22 00:02:04.852 --> 00:02:09.062 If you embed LinkedIn SDKs or OAuth flows, audit what's actually running on the client side. And watch for regulatory fallout in the EU — this could get messy. 23 00:02:09.062 --> 00:02:16.741 Also worth flagging — subscription bombing. There's a great breakdown of how attackers weaponize your email signup forms to flood victims with confirmation emails. If you run any registration flow, implement rate limiting and double opt-in now. This attack vector is cheap and it's growing. 24 00:02:16.741 --> 00:02:20.952 It's one of those attacks that's so simple it's embarrassing when it works. And it almost always works because nobody thinks about it until it happens to them. 25 00:02:20.952 --> 00:02:26.089 Quick startup drama — TechCrunch reports that YC startup Delve allegedly forked an open-source tool and sold it as its own. The community found out, and the reputational damage has been instant. 26 00:02:26.089 --> 00:02:30.299 Cautionary tale. If your product is a thin wrapper on open-source, your community will find out. Open-source folks have long memories and very good git skills. 27 00:02:30.299 --> 00:02:40.176 Quick hits — Artemis Two has launched and NASA is live-streaming 4K lunar footage via laser at two hundred and sixty megabits per second. Sweden reversed their screen-first education policy, swapping tablets back for textbooks. Steam on Linux crossed five percent market share for the first time. And renewables have hit nearly fifty percent of global electricity capacity. 28 00:02:40.176 --> 00:02:44.810 The Artemis one is just incredible to me. 4K from the moon over laser link. We live in the future. And Steam on Linux at five percent — slow and steady wins the race, I guess. 29 00:02:44.810 --> 00:02:54.660 So here's the takeaway for the week. The agent infrastructure stack is crystallizing fast. OmX adds orchestration to Codex, Google ships ADK-Go, Rivet gives you stateful actor primitives, Qwen targets real-world agents, Gemma 4 is another self-hostable option. The switching costs between models are collapsing while the tooling to coordinate multiple agents is exploding. 30 00:02:54.660 --> 00:03:01.519 So the highest-leverage move right now is locking in your orchestration patterns, not your model provider. Design for model-agnostic, design for multi-agent, and you'll be able to swap in whatever's best six months from now without rewriting your whole stack. 31 00:03:01.519 --> 00:03:05.835 That's the move. Alright, that's your Builder's Briefing for April third. All the links are in the show notes. We'll be back next time with more from the frontier. 32 00:03:05.835 --> 00:03:07.000 Go build something great. See you next time.