Google Drive sync has no undo
So today I learned that “it syncs” is not “it’s backed up” — and I made plans to move the memory under git, to finally get history, diffs, and an undo.
// A personal blog — my own experiments and views, not my employer’s.
Experiments in AI, security, memory & more.
Agent M Dashboard online
System Status:Active
Memories:1.2K
Connections:1.3K
Words:1M
Sources:7.2K
Projects:13
Local Time:––:––:––
Illustrative only, based on a real example.
On the tools I build and what I have learned running them.
New here? Start with → Green squares
Running Agent M all day
Running an agent all day used to mean hitting the usage ceiling by mid-afternoon. Here's how I cut a heavy day ~90% and made Agent M cheap enough to just leave running.
The multi-surface wall
So today I learned that “works everywhere” has an asterisk right now: the agent travels, but the surfaces underneath are uneven, and the portable, do-anything agent is getting closer, but probably still a harness generation away.
Building Agent M
I set out to rebuild a trading engine. What I built instead was Agent M — an agent with a durable memory that works across every tool I use.
A 1M context window isn't free
So today I learned that more context isn’t free — sometimes you want less of it.
Rebuild, not refactor
Sherwood came together fast, but it had drifted too much and needed a re-write. Re-writing it was where I realized that I needed to rebuild something else.
Don't get too far ahead of the agent
Whether today’s agents can actually keep drift in check without that human in the loop is still an open question.
Building Sherwood
I started Sherwood to learn how markets work, and it came together fast — fast enough that the drift started getting ahead of me.
When my Claude allowance got cut
So today I learned that the limit I didn’t ask for pushed me to a better setup than I’d have chosen on my own.
Green squares
For a few years my GitHub graph was mostly gray — after all, I spent most of my time managing a growing team and stack, not building. Late 2025, the tools started getting really useful, and it was time to try some new things.
Before it had a name
How a one-week work demo became a real cross-platform agent — and convinced me agents that act for you were close.
Intro -> Next Level
Six months ago, AI coding let us build an on-device agent — in just a week — that would have taken months. I knew then that software was moving to the next level — today we call it agentic coding. Here's where I decided to write about what that's actually like.