Ask HN: Prepping my first open-source release, would you use this?
I’ve been building an AI orchestration framework for the past few months, mostly for my own projects and I’m thinking about open-sourcing it soon. I’ve never done an open-source release before, so I’m looking for advice on how to launch it in a way that doesn’t just vanish into the GitHub void.
What it does (in short): - Orchestrates multiple AI agents with a clear structure for prompts and outputs. - Lets you add “firewalls” to filter or rewrite agent outputs before they go anywhere. - Has a chunking system for splitting big jobs into smaller tasks and running them in parallel. - Uses a database for persistence/concurrency (optional if people think it’s too heavy). - Very “plug-and-play”. Creating a new agent is basically making a folder and writing a prompt. - Built for “vibe coding”. Tools and filters are minimal boilerplate so you can hack them together fast.
I’d love to know from the HN crowd: Are there communities or use cases that would be interested in something like this?
When releasing open source, what makes you actually want to try or contribute to a new framework?
Would a strong focus on “vibe codability” be seen as a plus or just sloppy?
Not open source yet—just trying to make sure I launch it right when I do.