For most of the last decade I worked on large systems and the organisations around them. Seven years at T-Mobile as a senior solutions architect and technical product manager, a stint at GlobalLogic, then a year at Oracle as a Principal TPM working on cloud capacity and infrastructure. Different companies, same through-line: throughput, what breaks when you scale it, and getting engineering, product and operations to agree on what to do about it.
How that turned into Clayrune
In 2025 I started building something of my own. Like a lot of people I began with the stock market: I had a theory and thought I could build a system around it. The first version was me pasting code back and forth between ChatGPT and Visual Studio Code, one iteration at a time.
Then agents moved into the editor. Then Claude Code let me run several conversations at once. Every step was faster than the one before it, and every step created a problem the previous step did not have. I ended up with a screen full of terminal windows, no clear idea which agent was doing what, and the same explanations given over and over to sessions that had forgotten everything.
Eventually the obvious thing became obvious: I was spending more time managing agents than building. I wrote the whole story here.
So I built the thing I wanted. One place to see every project, every agent, and everything already decided.
It was called Mission Control for a while, a name Claude suggested. It is called Clayrune now, after the golem: a worker made of clay, brought to life by an inscribed word.
What I do now
I build Clayrune in the open. It is MIT-licensed, it runs on your own machine and your own Claude subscription, and a fair amount of what is in it today is there because somebody asked for it.
And I take on advisory work in the area I spent my career on: capacity planning, database optimisation, and cloud architecture for high-throughput systems, including fixed-scope capacity and architecture health checks.
Where to find me
If you are using Clayrune, thinking about using it, or it broke on you, I would like to hear about it. The same goes if you are building something adjacent, or just want to compare notes on running a lot of this at once. I read everything, and I answer.
Ron