The permissions this asks for feel kinda insane to me. Why does a kanban board need to see the code or my deploy keys among other things?
replies(2):
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.
- It's an early prototype so they haven't dealt with fine grained permissions
- They really do want to do things like access private repos with it themselves
- They really do want the ability to do things like checkout code, create PRs, etc... and that involves a lot of permission.
The other privacy complains I have regarding them harvesting usernames and email addresses... not so much.