Welcome to Agent Engineering Notes — here's what you're in for

When I started writing here in 2023, I was a DevOps engineer trying to make sense of what AI was doing to the job. The posts reflected that: how to survive the shift, how to explain it to leadership, how to not get replaced.

Then OpenClaw showed up.

I installed it on a Friday. By Saturday I had an agent running tasks overnight. By the following week I had restructured most of how I work, and I had a lot to say about it.

The DevOps framing quietly fell away. The last few months of posts have been almost entirely about agent systems — OpenClaw configuration, the Paperclip orchestration model, multi-agent coordination failures, what breaks when you hand a task to a machine and go to sleep. The newsletter URL still says “devopscareers” and I’m going to stop pretending that fits.

This newsletter is Agent Engineering Notes — what it has actually been for a while.

Agent engineering as a discipline. Not AI hype, not productivity tips, not “I used ChatGPT to write my emails.”

The real technical work of building systems where the AI is not the assistant — it is the system.

Specifically:

• How agent frameworks actually work under the hood — Paperclip, OpenClaw, what’s coming after them, and what each one is actually good at

• The engineering patterns that make agents reliable versus the ones that make them expensive chaos machines

• Memory, context management, tool design — the infrastructure problems nobody is writing about clearly yet

• Debugging and evaluation — what it looks like when an agent fails and how you find out before your users do

• Honest framework comparisons — without the sponsored-post energy or the benchmark theater

The goal is writing that a working engineer can open and do something with. Not inspiration. Craft.

If you came in through OpenClaw, Paperclip, or the agent posts — this newsletter was already for you. The OpenClaw briefing series, the multi-agent coordination piece, the security guide — that’s the vein I’m staying in and going deeper on. You’re not losing anything; you’re getting more of the thing that brought you here.

If you came in through the DevOps era — thank you. Those posts are still in the archive and they’re not going anywhere. But I’m not going back to that lane. If that’s what you subscribed for, I understand if you leave. No hard feelings.

The name of this newsletter has been sitting in my browser URL for months: agentengineeringnotes. I picked it almost by accident when I set up the profile.

It turns out I picked correctly.

— Alex

Building with agent systems and trying to make sense of the landscape? Forward this to someone who should be reading it

.