←back to thread

165 points louiskw | 1 comments | | HN request time: 0.211s | 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
barbazoo ◴[] No.44534333[source]
> human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks

This feel like much too broad a statement to be true.

replies(6): >>44534480 #>>44534494 #>>44534629 #>>44534963 #>>44535183 #>>44535505 #
1. ljm ◴[] No.44534494[source]
I wouldn't say it's the majority of my time but the most utility I've got out of AI is using MCP to deal with the boring shit: update my jira tickets to in progress/in review, read feedback on a PR and address the trivial shit, check the CI pipeline and make it pass if it failed, and write commits in a consistent, descriptive way.

It's a lot more hands on when you try to write code with it, which I still try out, but it's only because I know exactly what the solution is and I'm just walking the agent towards it and improving how I write my prompts. It's slower than doing it myself in many cases.