WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-03-03 1 00:00:00.000 --> 00:00:02.577 Good morning! Welcome to Builder's Briefing for March 3rd, 2026. I'm Alex, joined as always by Sam. 2 00:00:02.577 --> 00:00:06.872 Hey! Big show today — Google's making moves with MCP in the browser, Motorola is shipping de-Googled phones, and there's some great tooling drops. Let's get into it. 3 00:00:06.872 --> 00:00:18.144 Alright, so the headline: Google just shipped an early preview of something called WebMCP, which brings the Model Context Protocol directly into Chrome. Up until now, MCP has been a server-side and CLI thing — you hook up AI agents to tools and data sources on the backend. WebMCP flips that. Now your web app can expose structured capabilities — tools, resources, prompts — directly to AI agents running in or alongside the browser. 4 00:00:18.144 --> 00:00:24.053 Okay, this is a big deal. So instead of an AI agent puppeteering through your UI with something like Puppeteer, literally clicking buttons and scraping screens, it can just talk to your app natively through these MCP endpoints? 5 00:00:24.053 --> 00:00:31.498 Exactly. Think about an AI booking agent that wants to search flights on your travel site. Today, it's basically screen-scraping. With WebMCP, your site exposes a structured interface — here are my tools, here's how to search, here's how to book — and the agent just uses them directly. 6 00:00:31.498 --> 00:00:38.266 That's interesting because it's kind of like what REST did for app-to-app communication, but now it's for agent-to-app. And the timing is funny — there was a really popular Hacker News post arguing that MCP is overkill, that a well-structured CLI does the job. 7 00:00:38.266 --> 00:00:48.835 Right, and honestly that argument holds for local developer tooling. But WebMCP changes the calculus for anything web-facing. The browser is where your users are. Google is clearly betting that MCP becomes the interface layer between AI agents and the web. If you're building any kind of SaaS product, start prototyping an MCP manifest alongside your REST endpoints. The early-mover advantage here is real. 8 00:00:48.835 --> 00:00:52.089 Agents will prefer the apps they can talk to natively. That's a strong incentive. Alright, what else is happening in AI land? 9 00:00:52.089 --> 00:01:01.043 A couple of cool drops. EdgeQuake is a Rust-based GraphRAG implementation — so graph-based retrieval augmented generation — and it's inspired by LightRAG but written in Rust. If you've been eyeing graph RAG but the Python latency was a dealbreaker, this is production-grade and you can embed it directly in backend services without the GIL tax. 10 00:01:01.043 --> 00:01:07.395 The Rust ML ecosystem just keeps filling in. And speaking of tools, there's one called llmfit that auto-sizes LLM models to your hardware — your RAM, CPU, GPU — so you don't have to trial-and-error which quantization actually fits your machine. 11 00:01:07.395 --> 00:01:14.918 Super practical. And then there's Timber, which is pitching itself as quote 'Ollama for classical ML.' It claims three hundred thirty-six x faster than Python, which — take the benchmarks with salt — but the real value is making sklearn-style models as easy to serve as LLMs. Pull and run. 12 00:01:14.918 --> 00:01:22.988 I love that. Classical ML doesn't get enough love right now, and making it easy to deploy alongside LLM inference? That's a real gap being filled. Oh, and Anthropic refreshed their prompt engineering tutorial — if you're onboarding a team onto Claude, that's still the best free resource. Link in the briefing. 13 00:01:22.988 --> 00:01:29.808 Moving to dev tools — two things I want to highlight. First, there's a project called Memento proposing that full AI coding sessions should be captured as part of your git commit metadata. Like, the entire conversation you had with the AI while writing the code. 14 00:01:29.808 --> 00:01:35.040 Oh, that's provocative. On one hand, the auditability angle is huge — especially in regulated industries where you need code provenance. On the other hand, that's a lot of noise in your commit history. 15 00:01:35.040 --> 00:01:42.381 Yeah, the Hacker News thread — about a hundred seventy comments — was split right down the middle on that. But here's my take: AI-authored code is about to be the majority of diffs in a lot of codebases. You probably want to figure out your provenance story now, not after the fact. 16 00:01:42.381 --> 00:01:43.240 Fair point. What's the other one? 17 00:01:43.240 --> 00:01:50.243 A heads-up for Claude Code users. Anthropic's new Cowork feature is silently creating ten-gigabyte VM bundles on macOS. No warning, just eats your disk. They're tracking the issue but no fix yet. So if you're on a MacBook with limited storage, go check your disk usage. 18 00:01:50.243 --> 00:01:52.533 Ten gigs! Yeah, that'll sneak up on you fast on a two-fifty-six gig drive. Good to know. 19 00:01:52.533 --> 00:01:59.640 Okay, let's talk security because this was actually the biggest story of the day by points. Motorola announced a B2B partnership with GrapheneOS at MWC twenty-twenty-six. Fifteen hundred plus points on Hacker News. They're going to ship hardened enterprise phones together. 20 00:01:59.640 --> 00:02:05.965 That's wild. GrapheneOS has been the gold standard for privacy-focused Android, but it's always been a hobbyist, flash-it-yourself kind of thing. Motorola partnering officially? That legitimizes it as an enterprise security platform overnight. 21 00:02:05.965 --> 00:02:12.343 And it's not just GrapheneOS. The /e/OS project — which is a fully de-Googled Android fork — hit over five hundred points on HN the same day. The trend is unmistakable: demand for Google-free mobile is going mainstream, crossing into enterprise. 22 00:02:12.343 --> 00:02:18.617 So if you're building mobile apps and you assume Google Play Services is always there — push notifications through Firebase, maps through Google Maps — you might need a fallback path. Your next enterprise customer might literally require it. 23 00:02:18.617 --> 00:02:26.426 Exactly. Test on AOSP-based ROMs. It's not optional anymore. Also in security, quick one — a city called Everett dismantled its entire Flock surveillance camera network after a court ruled the footage is public record. That's a precedent-setter for anyone building IoT or civic tech with sensor data. 24 00:02:26.426 --> 00:02:29.029 Interesting. If you deploy sensors in public, the data might not stay private. Good to keep in mind. 25 00:02:29.029 --> 00:02:35.667 Quick hits! Apple dropped the M4 iPad Air, and simultaneously someone published a deep reverse-engineering series on the M4 Neural Engine. If you're optimizing CoreML models for on-device inference, that teardown is critical reading. Link in the briefing. 26 00:02:35.667 --> 00:02:43.971 Nushell keeps getting better for structured-data pipelines. Servo, the Rust-based browser engine, is gaining momentum as an embeddable web runtime — if Electron feels too heavy for your desktop app, Servo is approaching credible. And on a somber note, Felix 'fx' Lindner, legendary security researcher, has passed away. 27 00:02:43.971 --> 00:02:45.377 A real loss for the security community. Rest in peace. 28 00:02:45.377 --> 00:02:53.915 So here's the takeaway. The MCP ecosystem is splitting into two clear lanes: server-side CLI integration for developer tools, and browser-native WebMCP for web products. If users interact with your thing through a browser, start thinking about your MCP surface now — it's going to be how AI agents discover and use your product. 29 00:02:53.915 --> 00:02:58.757 And on the mobile side, de-Googled is going enterprise. If your app depends on Google Play Services, build that fallback path before your customers ask for it — because they're about to. 30 00:02:58.757 --> 00:03:01.855 That's the show for March 3rd. Links to everything we talked about are in the briefing. Thanks for listening, builders. 31 00:03:01.855 --> 00:03:03.000 Go build something great. See you next time!