April was a big month. Possibly too big. Between a critical RCE in Cursor, Anthropic shipping Opus 4.7 with three silent breaking changes, and the “ultra prefix” commercial model crystallising into something real, there’s a lot to unpack. I’m going to focus on the three things I can’t stop thinking about.

The Cursor CVE Should Have Been Front-Page News

Let’s start here, because this one genuinely alarmed me.

CVE-2026-26268 is a CVSS 9.9 remote code execution vulnerability in Cursor versions prior to 2.5. The mechanism is nasty: a malicious actor embeds a bare repository inside a legitimate-looking public repo, with a crafted pre-commit hook. When the Cursor agent runs a git checkout as part of a routine task — something agents do constantly — that hook fires automatically. No warning, no confirmation prompt, nothing. You just handed someone a shell.

March was a genuinely busy month in this space, and I’ve been sitting with a few of these developments over the past week trying to work out what’s noise and what actually changes how I work. Let me get into the things that stuck.

Sonnet 4.6 Is the Real Story, Not Opus

I’ll be honest — I’d been running Opus 4.6 as my default in Claude Code because it felt like the “serious” choice. That calculus is now just wrong.

The tech world is buzzing with another breakthrough in AI optimization - Sparse Transformers. Looking at the numbers being thrown around (2x faster with 30% less memory), my inner DevOps engineer is definitely intrigued. But let’s dive deeper into what this really means for the future of AI development.

The concept is brilliantly simple: why waste computational resources on parts of the model that won’t contribute meaningfully to the output? It’s like having a massive team where some members are essentially twiddling their thumbs during certain tasks. By identifying these “sleeping nodes” and temporarily sidelining them, we can achieve significant performance gains without sacrificing quality.

The developer tools landscape never ceases to amaze me with its constant evolution. Recently, I stumbled upon an interesting discussion about a new whiteboard IDE that combines Excalidraw’s canvas capabilities with Coder’s development environment management. The concept immediately caught my attention, particularly because it addresses a pain point I’ve experienced during remote collaboration sessions.

Working from my home office in Brunswick, I’ve often found myself juggling between different tools during technical discussions. There’s usually a whiteboard app open in one window, VS Code in another, and perhaps a terminal somewhere in the mix. The idea of combining these elements into a single, cohesive interface is genuinely exciting.