For about a year this hub was called cli.ceo, and the tagline was "the command line for software operations." It was accurate and it was wrong in the way accurate things sometimes are — it described the interface and missed the object.
The interface is a command line. Fine. But the command line isn't the thing. The thing is what the command line is about: how software actually gets built. For thirty years the industry versioned the product — the code, the artifacts, the deploys. Git owns that, and owns it completely. What stayed invisible was the process. How the software got made lived in senior engineers' heads, got narrated once in a throwaway agent transcript, and was gone the moment the terminal closed.
AI agents changed the physics of that. They emit the process as data — transcripts, runs, the changes they make, the decisions behind them. For the first time, how software gets built is a thing you can record, address, and keep. Git versioned the code. Now you can version the making of it.
Once you can record an act, you can do three things with it you couldn't before: capture it, watch it back, and govern it. That's the whole shape of what we're building. Capture lives in a separate tool, ceo-dna, on your own machine. Watch and govern live here, in the hub — and "watch how your software got built" is a genuinely strange and good sentence to be able to say.
I want to be straight about what that means today, because the easiest way to lose a skeptical operator is to describe a roadmap as if it were a product. What's shipped right now is the unglamorous, load-bearing part: the governance substrate. You can draft a change, hold it at a gate, ship it, and roll it back — and read the trail of who authorized what, when. That's it. That's real, and it's deployed, and we dogfood it on ourselves.
The parts that make people lean in — watching a real build replay as episodes, build provenance as a category regulators lean on, your team's house style governed across every machine — those are roadmap. Honestly roadmap. We'll light each one up on this site the day it's true, and not a day before. There's a version number in the bar at the top of every page; when it moves, it means a gate flipped, not that marketing got bolder.
So why rename it build.ceo? Because build is the object. It's the act and the thing the act produces. It's not an interface you happen to type into; it's what all of this is about. The command stays ceo — your muscle memory is safe. But the name now points at the work instead of the keyboard.
We think the making of software deserves a recording medium. We're building the boring half of it first.
— Lucia