←back to thread

Show HN: Vibe Kanban – Kanban board to manage your AI coding agents

(github.com)
171 points louiskw | 3 comments | 11 Jul 25 15:08 UTC | HN request time: 0.714s | source

Hey HN! I'm Louis, one of the creators of Vibe Kanban.

We started working on this a few weeks ago. Personally, I was feeling pretty useless working synchronously with coding agents. The 2-5 minutes that they take to complete their work often led me to distraction and doomscrolling.

But there's plenty of productive work that we (human engineers) could be doing in that time, especially if we run coding agents in the background and parallelise them.

Vibe Kanban lets you effortlessly spin up multiple coding agents. While some agents handle tasks in the background, you can focus on planning future work or reviewing completed tasks.

After a few weeks of internal dog fooding and sharing it with friends, we've now open-sourced Vibe Kanban, and it's stable enough for day-to-day use.

I'd love to hear your feedback, feel free to open an issue on the github and we'll respond ASAP.

Show context
gpm ◴[11 Jul 25 18:04 UTC] No.44535243[source]▶
Hmm, analytics appear to default to enabled: https://github.com/BloopAI/vibe-kanban/blob/609f9c4f9e989b59...

It is harvesting email addresses and github usernames: https://github.com/BloopAI/vibe-kanban/blob/609f9c4f9e989b59...

Then it seems to track every time you start/finish/merge/attempt a task, and every time you run a dev server. Including what executors you are using (I think this means "claude code" or the like), whether attempts succeeded or not and their exit codes, and various booleans like whether or not a project is an existing one, or whether or not you've set up scripts to run with it.

This really strikes me as something that should be, must legally be in many jurisdictions, opt in.

replies(5): >>44535477 #>>44535579 #>>44536029 #>>44536787 #>>44536953 #
bn-l ◴[11 Jul 25 18:27 UTC] No.44535477[source]▶
Thanks, really appreciate the heads up. I put devs who do this on a personal black list for life.

I think also that this would be better as an mcp tool / resource. Let the model operate and query it as needed.

replies(1): >>44536414 #
willsmith72 ◴[11 Jul 25 20:17 UTC] No.44536414[source]▶
It's the email/username harvesting that you mean right? Or do people also have something against anonymised product analytics?
replies(3): >>44536675 #>>44539259 #>>44541030 #
adastra22 ◴[12 Jul 25 10:44 UTC] No.44541030[source]▶
Yes to both.
replies(1): >>44541785 #
willsmith72 ◴[12 Jul 25 13:04 UTC] No.44541785[source]▶
how do you build a product without analytics? how do you measure the success and failure of every change?
replies(2): >>44541797 #>>44543084 #
1. msgodel ◴[12 Jul 25 13:06 UTC] No.44541797[source]▶
Many users tend to be pretty vocal when changes break things they like, you don't need to spy on them for that. Mail readers > analytics frameworks.
replies(1): >>44542172 #
2. willsmith72 ◴[12 Jul 25 14:07 UTC] No.44542172[source]▶
"not breaking things they like" is a very low bar for building a great product

To be honest building things this way seems like such a competitive disadvantage I don't see how it could ever work at scale. Certainly all the big players are using them. If we shake our heads at the little players doing the same, we're just going to widen the moat

replies(1): >>44544174 #
3. adastra22 ◴[12 Jul 25 18:56 UTC] No.44544174[source]▶
Spying on your users does not give better feedback than simply asking your users (surveys, focus groups) and responding to the considered comments you receive. Spying and trying to infer intent is such a low bar to improve upon.