WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-03-10 1 00:00:00.000 --> 00:00:07.688 Good morning and welcome to Builder's Briefing for March 10th, 2026. I'm Alex, joined as always by Sam, and today — the agent tooling layer is growing up fast. We've got native sandboxing for AI agents, a huge plugin library for Claude Code and Codex, and a fascinating look at how living brain cells are playing DOOM. 2 00:00:07.688 --> 00:00:13.418 Yeah, it's one of those days where you look at the front page and realize, oh, we're past the 'can agents do stuff' phase. Now it's all about 'how do we stop them from wrecking everything while they do stuff.' Love it. Let's get into it. 3 00:00:13.418 --> 00:00:24.563 So the big story — Agent Safehouse just dropped. It's a macOS-native sandbox built specifically for local AI agents. It hit over five hundred points on Hacker News, and the pitch is simple: if you're running autonomous agents that touch your filesystem or execute shell commands, you've basically been running without a seatbelt. This gives you process-level isolation using macOS sandbox profiles, so you define exactly what an agent can access before it runs. 4 00:00:24.563 --> 00:00:34.282 Right, and what's wild is how many people have been reaching for Docker or full VMs just to safely test agent tool-use locally. That's a massive amount of overhead for what should be a simple permission boundary. This gives you native-speed sandboxing with granular controls. If you're building with Claude Code or Codex or any local agent loop, there's really no excuse not to use something like this. 5 00:00:34.282 --> 00:00:41.293 Exactly. And the timing is perfect because there's a whole parallel conversation trending right now about FreeBSD Capsicum versus Linux Seccomp — two different OS-level sandboxing models. The signal from the community is clear: sandboxing is table stakes for agents now, not a nice-to-have. 6 00:00:41.293 --> 00:00:46.806 I'd honestly be surprised if every serious agent framework doesn't have native sandboxing integrated or announced within six months. If you're building an agent platform and you're not thinking about this, you're already behind. 7 00:00:46.806 --> 00:00:54.349 Speaking of agent tooling maturing — there's a repo called claude-skills that packages a hundred and sixty-nine production-ready plugins for Claude Code, Codex, and OpenClaw. Engineering, marketing, compliance, even C-level advisory workflows. You install via a plugin marketplace and start composing right away. 8 00:00:54.349 --> 00:01:02.931 A hundred and sixty-nine! That's a real ecosystem forming, not just a handful of demos. For anyone building on top of these coding agents, that's weeks of custom prompt engineering you can skip. I love that it spans beyond just engineering too — compliance and marketing plugins tell you something about where agent adoption is actually happening in orgs. 9 00:01:02.931 --> 00:01:10.595 There's also BettaFish, which is a multi-agent system for public sentiment analysis — and here's the kicker — it's built from scratch with zero dependencies. No LangChain, no framework at all. It predicts trends, breaks filter bubbles, and it's worth studying just to see how far you can get with pure implementation. 10 00:01:10.595 --> 00:01:17.002 That's interesting because there's been this growing backlash against framework overhead in the agent space. Sometimes the abstraction costs you more in debugging and performance than it saves you in setup time. BettaFish is kind of a proof point for that argument. 11 00:01:17.002 --> 00:01:23.723 One more on the AI side — there's an essay making the rounds arguing that Knuth's literate programming deserves a second look in the agent era. The idea being that code interwoven with human-readable explanation is exactly what AI agents need to work effectively with codebases. 12 00:01:23.723 --> 00:01:31.387 Oh, I actually read that one. It clicked for me because — think about it — we keep throwing more context window at the problem of agents understanding code, but what if the code just explained itself better? Writing code that's legible to both humans and machines might be the underrated unlock nobody's investing in. 13 00:01:31.387 --> 00:01:38.592 On the dev tools side, two things caught my eye. First, Neko — a self-hosted virtual browser running in Docker with WebRTC streaming. Seventy-five hundred engagement points. It's essentially a headless browser you can watch and interact with remotely, which is huge for agent-based browser testing. 14 00:01:38.592 --> 00:01:44.370 If you're building anything where agents need to interact with web pages, having an isolated browser environment you can observe in real time is incredibly useful. It pairs nicely with the sandboxing theme too — containment at every layer. 15 00:01:44.370 --> 00:01:51.212 And then ast-grep — structural code search and rewriting using AST patterns instead of regex. If AI agents are writing code into your codebase, and let's be honest, they increasingly are, structural search is how you enforce patterns at scale. Link in the briefing for both of those. 16 00:01:51.212 --> 00:01:57.594 Yeah, regex for code search was always a hack. AST-level matching is the right abstraction, especially when you've got agents generating code that might be syntactically correct but structurally inconsistent with your patterns. That's a real maintenance time bomb. 17 00:01:57.594 --> 00:02:04.823 Quick security note — beyond the Capsicum versus Seccomp comparison we mentioned, there's a fascinating deep dive on how /proc/self/mem in Linux can bypass page permissions to write to unwritable memory. If you're building sandboxing or memory protection, you need to understand this attack surface. 18 00:02:04.823 --> 00:02:11.206 That's the kind of thing that makes you go 'wait, what?' It's one of those Linux quirks that's been there forever but becomes way more relevant when you're trying to contain untrusted code — or untrusted agents. Definitely worth the read if you're security-minded. 19 00:02:11.206 --> 00:02:14.228 Alright, rapid fire quick hits. Living human brain cells are playing DOOM on a CL1 chip. I'll just let that sit for a second. 20 00:02:14.228 --> 00:02:17.588 I mean — of course they are. Everything eventually runs DOOM. But biological neurons doing it? That's genuinely mind-bending. Pun intended. 21 00:02:17.588 --> 00:02:23.608 We've also got a comprehensive single board computer buyer's guide for twenty twenty-five, a full tutorial on procedural hex maps using Wave Function Collapse, and someone made a programming language with M&Ms, which is absurd and I kind of love it. 22 00:02:23.608 --> 00:02:29.290 The M&Ms one — you have to respect the commitment. And honestly, the RSS renaissance piece is worth a click too. 'The death of social media is the renaissance of RSS' — feels like that's been true for a lot of builders for a while now. 23 00:02:29.290 --> 00:02:38.549 So stepping back — today's theme is unmistakable. Sandboxing, task management, plugin ecosystems, framework-free multi-agent design — the market has moved past 'can agents work' to 'how do we safely and reliably ship with them.' The teams that treat agent safety and observability as first-class concerns right now are going to ship faster than those bolting it on after an incident. 24 00:02:38.549 --> 00:02:43.820 One hundred percent. It's the classic infrastructure lesson — invest in guardrails before you need them, not after something breaks. The tooling is there now. There's no excuse to be running agents without containment. 25 00:02:43.820 --> 00:02:49.743 That's Builder's Briefing for March 10th. All the links and repos we mentioned are in the show notes. If you're building with agents, go check out Agent Safehouse today — seriously, today. We'll be back tomorrow with more. Until then, ship safe. 26 00:02:49.743 --> 00:02:51.000 Ship safe. And sandbox everything. See you tomorrow!