About

I kept losing track of my own tooling. Scripts scattered across READMEs, Makefiles, and shell history — no single place to see what I could even run, let alone how.

Over the last couple of years I've been building something that finds every command in your projects and gives you one place to run them. Something I picked up on early in my career is that the CLI is power, and AI honestly has solidified that as a paradigm.

There's been a lot of different things I struggled with in my own workflow:

• How do I manage my secrets? Became the vault.
• How do I find what previously ran? Became the logger system.
• How do I serialize work or parallelize work? Became some of my more advanced runners.
• How do I run things in the sandbox? Became my container feature.

It started off as a terminal UI and has recently transformed into a desktop app that reps this terminal UI.

I actually didn't realize the agent problem until about a year ago, when I started using AI a lot more in my development. It was making decisions and running things, and while I could follow along, it didn't always give me a clear sense of what was actually happening without feeling super overwhelmed.

Flow was already the surface that allowed me to control this overwhelming world.

Given the current shift in AI development, I began building on top of what I'd made so AI could use it too — and so I'd have the tools for working with AI.

It's been invigorating seeing Mochi take Flow to the next level.