What Vibe Kanban Does
Vibe Kanban addresses what BloopAI CEO Louis Knight-Webb calls the doomscrolling gap: the unproductive waiting time when a coding agent thinks and the developer has nothing constructive to do. Rather than watching one agent work, developers plan tasks on a kanban board and dispatch multiple agents to isolated workspaces simultaneously. The tool has grown to 27K+ GitHub stars with 280+ releases, indicating sustained development investment rather than a one-time launch.
Workspace Isolation and Agent Compatibility
The workspace isolation model is the technical foundation that makes everything else work. When a card moves to In Progress, Vibe Kanban provisions a Git worktree that gives the agent its own copy of the codebase on a dedicated branch. A managed port daemon allocates a free network port for the dev server, preventing the collisions that plague naive attempts at running multiple agents through tmux or separate terminal windows. Each workspace operates independently with its own terminal session and browser preview.
Agent compatibility covers the major AI coding tools without locking developers into a single ecosystem. Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR, and Qwen Code are all supported through a unified workspace interface. Switching between agents per workspace is seamless, allowing teams to use different tools for different types of tasks based on their strengths. This agent-agnostic approach future-proofs the investment as the AI coding landscape evolves.
Code Review and MCP Integration
The code review workflow within Vibe Kanban reduces context switching significantly. Inline diff viewing shows exactly what the agent changed, comment threads allow directing feedback to specific lines, and the agent can respond to comments within the same session. Pull request creation with AI-generated descriptions flows directly from the review into GitHub or GitLab without opening additional browser tabs. The built-in browser preview with devtools, inspect mode, and device emulation catches visual regressions before code leaves the workspace.
The bidirectional MCP integration elevates Vibe Kanban from a simple project board to programmable infrastructure. As an MCP client, it connects to external servers like Postgres and Brave Search, exposing those capabilities to agents working within workspaces. As an MCP server, it exposes the board itself as an API that other agents can manipulate: creating tasks, moving cards, reading board status, and querying project state. This enables higher-level orchestration where one agent manages the project while others execute individual tasks.
Rust Backend and Self-Hosting
The Rust backend with Cargo Workspaces delivers the performance characteristics that workspace orchestration demands. SQLite stores workflow state locally without cloud dependency, while Git manages code state through worktrees. This separation means the kanban board is not committed to the repository and lives as a local development tool rather than project infrastructure. The trade-off is that board state does not synchronize automatically across team members unless the cloud option is enabled.
Self-hosting is well-supported with comprehensive documentation covering reverse proxy configuration, remote SSH editor integration, and environment variable setup. The Tauri-based desktop app provides a native experience on macOS, Linux, and Windows, while the web interface works through any browser. Cloudflare Tunnel and ngrok integration documentation makes remote access straightforward for developers running Vibe Kanban on headless servers.
Development Cadence and Limitations
The active development cadence shows consistent feature additions rather than maintenance-only releases. Recent versions added Azure DevOps repository support, live diff streaming that self-corrects as agents work, and crash recovery with localized error screens. The 3,200+ issues and pull requests from community contributors indicate genuine adoption beyond the initial star surge, with feature requests focusing on practical workflow improvements rather than cosmetic changes.
Limitations become apparent in specific scenarios. Each Git worktree may need its own node_modules directory, consuming significant disk space for JavaScript-heavy projects with many parallel workspaces. The local-first architecture means team visibility requires either the cloud option or manual board sharing. The kanban interface does not support task dependencies or hierarchical subtask decomposition, limiting its planning capabilities compared to dedicated project management tools.
The Bottom Line
Vibe Kanban fills a unique position in the developer toolchain by solving the parallel agent execution problem that no other tool addresses as completely. The combination of workspace isolation, multi-agent support, inline code review, and MCP integration creates a coherent workflow from task planning through code delivery. For developers who have outgrown running one agent at a time and want structured orchestration without giving up local-first simplicity, Vibe Kanban is the most mature option available.