←back to thread

163 points louiskw | 1 comments | | HN request time: 0.208s | 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
remram ◴[] No.44534052[source]
Why do you need to "manage" your coding agents like they are people? How long does it take them to do a task once prompted, in the background?

Don't you just prompt an immediately review the result?

replies(3): >>44534186 #>>44534189 #>>44534954 #
1. gpm ◴[] No.44534954[source]
Currently - claude code is pretty slow. I've definitely had it take >15 minutes on the (faster than opus!) sonnet model just thinking and writing code without feedback or running long lasting tools. I expect this to change given that companies like cerebras exist and seem to know how to generate tokens in much less time, but the current state of the art is what it is.

Always - if you're going to pipe the result of some slow process back to them (like building a giant C++ project that takes minutes/hours, or running a huge set of tests...)... it's going to be slow.