Most pieces about new AI capabilities read like a datasheet. Faster, bigger, more. They are not much use, because a capability only means something once someone shows what they do with it.
So no list. This is what Claude can now do for me that it could not a year ago, seen from my own desk.
This is part 3 of a series. In part 1 I left WordPress, in part 2 the assistant shifted from advisor to operator. Here it gets practical.
It works in my real stuff
The biggest change does not show up in a demo. It is that Claude works inside my own environment. My files, my site, my channels. Not a clean example project, but the messy reality I sit in every day.
A year ago I handed over context by pasting it in. Now it reads the folder, sees the structure, and adapts to how I already did things instead of imposing its own version. That difference sounds small and changes everything. It is the gap between someone advising on your work and someone who knows your work.
It keeps going while I do something else
What surprised me most: I can set a task down and move on to something else. The image generation for a cover runs for a few minutes in the background while I write the text. A bigger job I can let run, and I get a nudge when it is done.
That changes the tone of the work. It feels less like a tool I operate and more like something working beside me. I dislike that comparison when it gets stretched too far, but on a small scale it holds: the waiting has been taken out of the loop.
It bends to my way of working
The capability I least expected to value is the set ways of working I can lock in. My writing voice, my rules, my fixed review steps. Written down well once, and from then on it carries them every time.
For me that means, concretely: I write Dutch and English separately, no literal translation, and after every text a fixed cleanup pass runs over it to strip the AI tells. That is no longer something I have to force case by case. It is built into how I set it up.
My image pipeline is the sharpest example. I built a small script once that generates an image locally, optimizes it, and drops it in the right place on my site. Since then a cover is one instruction. No stock site, no subscription, no plugin. The cover on this piece was made that way.
Where I still keep my own hand on it
None of this takes the human out of the loop, and I do not want it to. In the previous part I described my rule: Claude may execute where I see the result, but nothing leaves quietly. That rule still holds, precisely because it can now do more.
Because that is the real shift of the past year. It is not that the answers sound smarter. It is that the assistant has moved closer to my actual work, can keep going while I live my day, and bends to how I want to work. That is worth a lot. It is also exactly why I keep looking before anything goes live.
The capabilities grow faster than my getting used to them. That is not a complaint. It is why I wrote this series: not to talk up the technology, but to keep clear for myself where the convenience stops and my judgment begins.
This is part 3 of a series on AI as an operator. Start at part 1: how I left WordPress behind.