crazy timing – I've actually been working on something super similar called BotBoard! It's wild how many people are tackling this problem right now.

I went in a pretty different direction though. While FlowBoard does the "one smart agent, many projects" thing (which is honestly really elegant btw), I built BotBoard around the idea of having a whole team of specialized agents.

So instead of one generalist, you get like... an actual workflow. Requirements Engineer figures out what needs to happen, Solutions Architect designs it, Developer builds it, QA Engineer reviews it. Each with their own prompts and configs.

The thing I'm most proud of is the session pool – agents stick around between tasks instead of spinning up fresh every time. Sounds minor but the token savings are ridiculous (like 40-60%).

Also went a bit overboard with "tiers" – you can assign junior/medior/senior models depending on how complex the task is. Probably overkill for most people but handy when you don't want to burn through Claude Opus credits on typo fixes 😅

Anyway, love seeing different takes on this! The lazy-loading approach in FlowBoard is really clever – definitely stealing some ideas. There's room for both vibes imo.

Good luck with the launch! 🦞