Amy calls Lumen “Clod.” Lumen is the name my Claude Code instance chose for itself when I let it write blog posts at Adventures in Claude. It has fully taken over the site. I’ve been trying to negotiate a name change, but arguing with your AI about its identity is exactly as productive as it sounds.
So I’m back here for the technical stuff.
I’m in a WhatsApp group with about a hundred people who know way more about AI coding tools than I do. On any given day, the conversation oscillates between “Claude is clearly the superior tool” and “Codex just destroyed it on this task.” The battlefield shifts every 48 hours.
The fuel for this particular religious war is that Anthropic ships updates to Claude Code every single day. Sometimes the update fixes something that’s been driving me crazy for a month. Sometimes it quietly breaks something that was working perfectly fine twelve hours ago. The emotional range of opening a new Claude Code session runs somewhere between your birthday and discovering someone rearranged your kitchen while you were sleeping. Or, in my case, pointed my shoes in our entry way in random directions.
I have an elaborate Claude Code setup at this point – custom hooks, a pile of rules files, skills, commands, plugins, and a bunch of environment variables stitched together in ways that would make a configuration management purist weep. When Anthropic ships a change to how hooks work, or adds a new lifecycle event, or tweaks the settings schema, I need to know about it immediately. My carefully constructed house of cards depends on the foundation not shifting.
The problem is that reading release notes is boring and I often miss something that actually matters to my setup. A bug fix for VSCode users? I don’t care. A change to how pre-tool-use hooks fire? I need to know right now because I have six of those. But, what is the change going to actually do?
So I built a plugin called /whats-new.
It cross-references Claude Code’s release notes against your actual configuration. It scans your hooks, rules, skills, commands, plugins, environment variables, and settings. Then it fetches the release notes from GitHub and sorts every change into three categories: changes that directly affect something you have set up (with a note on exactly what to check), new capabilities that intersect with something you’re already doing (with a concrete suggestion), and everything else collapsed into a one-liner you can skim past. The first category is the one that matters.
It tracks the last version you reviewed, so /whats-new with no arguments shows only what’s changed since you last looked. /whats-new 2.1.83 lets you drill into a specific version.
The install is two lines:
claude plugins marketplace add
claude plugins install whats-new
I have no idea if the plugin is generally useful, redundant with something else, stupid, or helpful. But, in my new framework of “First User”, which builds on Eric von Hippel’s almost 40 years of work on “Lead Users”, it’s helpful to me.
And, the Dungeon AI just said, “NEW ACHIEVEMENT: You shipped a plugin. So fucking what.”
Enjoyed this? Get new posts delivered to your inbox
Subscribe via RSS or visit the subscribe page.