WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-05-24 1 00:00:00.000 --> 00:00:01.860 Hey everyone, welcome to Builder's Briefing for May 24th, 2026. I'm Alex. 2 00:00:01.860 --> 00:00:07.464 And I'm Sam. We've got a packed one today — Anthropic drops some big interpretability news, Microsoft is yanking Claude Code licenses from employees, and Apple is publishing formal verification playbooks for crypto code. 3 00:00:07.464 --> 00:00:13.985 Let's dive right in. So the big story today — Anthropic published an initial update on something they're calling Project Glasswing. The Hacker News thread already has almost four hundred points and over two hundred comments, so people are paying attention. 4 00:00:13.985 --> 00:00:19.386 Yeah, and what caught my eye is the framing. This isn't about making Claude faster or scoring higher on benchmarks. This is about making the model's reasoning transparent and interpretable at a fundamental level. 5 00:00:19.386 --> 00:00:28.123 Exactly. And for builders, the practical implication is huge. Think about it — if you're shipping Claude into a healthcare app or a financial compliance tool, right now explaining why the model made a specific decision is basically a black box problem. Glasswing suggests future Claude versions might ship with built-in interpretability hooks. 6 00:00:28.123 --> 00:00:35.256 So like stack traces for model reasoning? That's a game changer for anyone doing AI safety audits. I've been on teams where we spend weeks trying to explain model behavior to compliance reviewers. If you could just pull a reasoning trace from the API, that collapses so much work. 7 00:00:35.256 --> 00:00:45.268 Right. And the strategic signal here is that Anthropic is differentiating on trust infrastructure. If you're in enterprise sales and your procurement team is choosing between model providers, interpretability as an API feature is the kind of moat that actually matters. Builders in regulated industries — healthcare, finance, government — should be tracking this closely. Link in the briefing. 8 00:00:45.268 --> 00:00:47.102 It's smart positioning. Benchmarks get commoditized fast. Trust doesn't. 9 00:00:47.102 --> 00:00:52.273 Okay, so speaking of trust and vendor relationships — this next one is spicy. Microsoft has started canceling Claude Code licenses for internal employees, reportedly pushing teams toward Copilot instead. 10 00:00:52.273 --> 00:00:57.623 Oh, this is the vendor lock-in story playing out in real time. And it's not just a Microsoft internal thing — if your organization gets Claude Code access through Microsoft licensing, you might be affected too. 11 00:00:57.623 --> 00:01:02.743 Yep. The immediate action item is check your access right now and make sure you have a direct Anthropic plan as a backup. Don't let a bundled deal be your single point of failure for developer tooling. 12 00:01:02.743 --> 00:01:08.118 That's interesting because it also shows how competitive the AI coding tool space is getting. Microsoft clearly wants everyone on Copilot, and they're willing to use their licensing leverage to make that happen. 13 00:01:08.118 --> 00:01:15.404 On a lighter note in dev tools — there's a cool open source project called Kanbots that caught my eye. It's a desktop Kanban board where each card can spawn its own AI agent running in parallel. So imagine a task board where every ticket literally has a coding assistant attached to it. 14 00:01:15.404 --> 00:01:22.052 Oh, that's neat. So instead of running agents from the command line and juggling terminals, you get a visual orchestration layer. I could see that being really useful for managing multi-agent workflows where you want to see at a glance what each agent is doing. 15 00:01:22.052 --> 00:01:27.733 Also worth a quick mention — Microsoft shipped C# memory safety improvements. New compiler-level checks for null safety and span-based memory access. Basically Rust-like safety guarantees without leaving the .NET ecosystem. 16 00:01:27.733 --> 00:01:30.790 As someone who's written a lot of C#, that's long overdue. If you're on .NET, update your analyzers and start opting in. 17 00:01:30.790 --> 00:01:36.471 Alright, shifting to AI and models. There's an open-source dataset that just dropped — seven hundred fifty-four structured cybersecurity skills for AI agents, mapped to five major frameworks including MITRE ATT&CK and NIST. 18 00:01:36.471 --> 00:01:43.298 Right, and what's wild is you can plug this directly into Claude Code, Copilot, Cursor, and over twenty other platforms through the agentskills.io standard. If you're building security-aware agents, this saves you months of hand-rolling your own threat model mappings. 19 00:01:43.298 --> 00:01:49.794 We'll come back to that in takeaways because it ties into a bigger theme. Also trending — there's a fantastic guide called 'Making Deep Learning Go Brrrr from First Principles' that walks through GPU utilization, memory bandwidth, and compute bottlenecks. 20 00:01:49.794 --> 00:01:55.067 I've actually read that one. If you're fine-tuning models and wondering why your GPU is sitting at forty percent utilization, it does the actual math to show you where the bottleneck is. Highly recommend it. 21 00:01:55.067 --> 00:01:58.506 Okay, security section. A few big stories here. First — CISA is dealing with a significant data leak and Congress is demanding answers. 22 00:01:58.506 --> 00:02:03.091 Yikes. If you work with any CISA-shared threat intelligence feeds or you've submitted anything to their vulnerability disclosure programs, you should verify your data exposure now. 23 00:02:03.091 --> 00:02:09.944 And then Apple published something really cool — a detailed blueprint for how they're using formal verification to prove correctness of their Corecrypto library. This isn't academic hand-waving, it's a concrete playbook for applying formal methods to real-world C code. 24 00:02:09.944 --> 00:02:15.370 That's huge for anyone maintaining crypto implementations. Formal verification has always been this thing people talk about but rarely show their work on. Apple actually showing the process is incredibly valuable. 25 00:02:15.370 --> 00:02:22.808 And one more — Oura, the smart ring company, confirmed they receive government requests for user health data but won't say how many. Quick reminder if you're building health or wearable products: architect your data storage with user-controlled encryption before that first subpoena shows up. 26 00:02:22.808 --> 00:02:25.687 Quick hits before we wrap up. There's a Wayland compositor running inside Minecraft — because of course there is. 27 00:02:25.687 --> 00:02:29.126 Ha! I love these. Also, the FBI reportedly wants near real-time access to US license plate readers, which is... significantly less fun. 28 00:02:29.126 --> 00:02:36.029 Jeff Geerling covered a wireless time sync solution called Wi-Wi that hits sub-five nanosecond accuracy. If you're doing financial trading, sensor fusion, or distributed databases where clock drift matters, this could replace PTP and GPS setups at a fraction of the cost. 29 00:02:36.029 --> 00:02:42.118 Sub-five nanoseconds wirelessly? That's genuinely impressive. And there's the z three eighty-six story — someone fully disassembled the original 80386 microcode and there's an open-source hardware reimplementation being built on top of it. 30 00:02:42.118 --> 00:02:49.200 Okay, two big threads to pull on from today. First — the AI coding tool landscape is fragmenting. Microsoft yanking Claude Code licenses is a clear signal. Never depend on a single vendor's bundled AI tooling. Keep direct relationships with the model providers you actually use. 31 00:02:49.200 --> 00:02:56.460 Totally. And second — cybersecurity for AI agents is becoming a real structured discipline now, not an afterthought. That seven hundred fifty-four skill framework mapped to MITRE ATT&CK gives you an actual starting point for scoping what your agents should and shouldn't be able to do. 32 00:02:56.460 --> 00:02:58.650 Don't wait for a breach to define your agent security posture. That's the bottom line. 33 00:02:58.650 --> 00:03:00.434 Well said. Links to everything we mentioned are in the briefing notes. 34 00:03:00.434 --> 00:03:03.592 That's it for May 24th. We'll see you next time — keep building, keep shipping, and keep those vendor contracts diversified. 35 00:03:03.592 --> 00:03:04.000 Later, everyone!