It is harvesting email addresses and github usernames: https://github.com/BloopAI/vibe-kanban/blob/609f9c4f9e989b59...
Then it seems to track every time you start/finish/merge/attempt a task, and every time you run a dev server. Including what executors you are using (I think this means "claude code" or the like), whether attempts succeeded or not and their exit codes, and various booleans like whether or not a project is an existing one, or whether or not you've set up scripts to run with it.
This really strikes me as something that should be, must legally be in many jurisdictions, opt in.
I will leave this open for comments for the next hour and then merge.
Their reliability probably varies a lot depending on what you are using them for - so maybe I'm just using them in more difficult (for claude) domains.
This is a bet that coding agents will continue to get better, and this feels like the right time to try and figure out the interface.
But that's not a today problem, we just want to absorb feedback and iterate until we build the ultimate tool for working with these coding agents.
Things move across the board so quickly when AI is doing the work that ~50% of the columns seem pretty redundant.
Outside of that, really enjoying the flow.
BTW, if anyone’s juggling multiple agents and wants a “quarantine” layer before changes hit Git, I’m hacking on SAV (Shadow VCS)open source, risk scores every commit and keeps them sandboxed until you approve. Happy to swap notes. https://github.com/AKIFQ/sav