Ran Vibe Kanban on a side repo over the weekend it’s slick, but I tripped on one thing: all the agents write into the same checkout, so parallel cards can clobber each other when they touch the same files. I’ve been spinning up a quick `git worktree` per card as a stop gap.

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

Are you sure you're using vibe-kanban? The project spins up a worktree for each task attempt specifically to solve this problem.

How is the isolation layer of a shadow vcs different/better than just checking into a feature branch and not pushing?

Not saying there isn't value in the risk assessment part, but, I'm asking specifically about the change isolation.