←back to thread

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

(github.com)
163 points louiskw | 2 comments | 11 Jul 25 15:08 UTC | HN request time: 0.451s | 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 ◴[11 Jul 25 16:49 UTC] 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 #
rvz ◴[11 Jul 25 17:09 UTC] No.44534629[source]▶
I read that too and these are the kind of statements which really tells you what happens when a profession embraces mediocrity and accepts something as crass as "Vibe-coding" which is somehow going to change "software engineering" even when adding so-called "AI agents" - which makes it worse.

All this cargo-culting is done without realizing that more code means more security issues, technical debt, more time for humans to review the mess and *especially* more testing.

Once again, Vibe-coding is not software engineering.

replies(1): >>44536259 #
1. skeeter2020 ◴[11 Jul 25 19:56 UTC] No.44536259[source]▶
and I came into the industry when software was not engineering. Still think this is mostly true (you can call yourself an engineer when you insure your product)
replies(1): >>44539659 #
2. Disposal8433 ◴[12 Jul 25 05:52 UTC] No.44539659[source]▶
You're right and it's sad. Instead of being more serious about the output of our work, we put everything in the trash and removed all barriers and tools to would have hardened the code. The processes to plan, write specs, and check applications went the way of the dodo too.

I'm glad I work for a regulated industry where we still have some kind of responsibility and pride for what we do. I could never work for the kind of irresponsible anarchy that AI is creating.