My personal CLI-replacement tool for running multiple MVPs solo—should I open-source it?

I built a CLI-replacement tool for my own use. It's mainly meant for solo use and for fast MVP development, so I use it to work on and manage several projects at the same time.

You might ask whether a tool like this is even necessary, but for me it is—because it accumulates the common standards shared across all my projects, along with per-project issue management and a running history, which lets me run projects in a way that's perfectly tailored to how I like to work.

It took me about two weeks to build, mostly because I wanted to define every little detail one by one. The framework itself, of course, I threw together quickly with Claude.

I've built out a persona/agent system: when I ask it to do this or that, it dispatches the right agents on its own, creates Git issues, and runs across the whole project. It also has a dispatch feature, so I can run it from outside without my laptop—which is genuinely convenient.

I'm torn about open-sourcing it for free, but I'm not sure anyone would actually use it. There's quite a bit I'd need to clean up to open-source it, though... maybe I should just put it out there........

I feel like it could be a big help for non-developers trying to start something without a developer—but these days people just build and deploy with AI right in the browser, so they might actually prefer that over this kind of more old-school, hands-on management. For me, though, the real advantages are Git history management and accumulating.

Anyway, I feel like a SaaS tool like this could be genuinely useful for people working in certain specific fields/professions—but I'll need to think it over a bit more.

If you have an interests, email me 👉 lief.ofcl@gmail.com