←back to thread

163 points louiskw | 3 comments | | HN request time: 0.479s | 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.

1. oc1 ◴[] No.44533641[source]
We need something like a kitchen brigade in software - one who writes the vibe code tickets (Chef de Vibe), one who reviews the vibe code (Sous-Vibe), one who oversees the agents and restarts them if they get hung up (Agent de Station). We could theoretically smash thousand tickets a day with this principle
replies(2): >>44533873 #>>44540089 #
2. ggordonhall ◴[] No.44533873[source]
Completely agree!

You can actually use a coding agent to create tickets from within Vibe Kanban. Add the Vibe Kanban MCP server (from MCP settings) and ask the agent to plan a task and write tickets.

3. atavistically ◴[] No.44540089[source]
c.f. "Surgical Team" in 'The Mythical Man-Month' by Fred Brooks. That book is perennially relevant.