vibe-kanban

Whether this skill alone is sufficient: Manage multiple AI agents (Claude/Codex/Gemini) from a single Kanban board. Moving a card (task) to In Progress automatically creates a git worktree and starts the agent. Verified versions (as of 2026-02-22) Browser opens automatically. ⚠️ Port conflict warning : If another dev server like Next.js is using port 3000, run PORT=3001 npx vibe-kanban --port 3001 . Confirm Main server on :3001 in the startup log, then visit . Normal startup log: Set in .env file before starting the server. API key location per agent (Settings → Agents → Environment variables) Vibe Kanban runs as an MCP (Model Context Protocol) server, letting agents control the board directly. ~/.claude/settings.json or project .mcp.json : Add to ~/.config/opencode/opencode.json : After restarting, vk_* tools are available directly in your OpenCode session. ⚠️ Tool name changes from older versions : vk_list_tasks → vk_list_cards , vk_create_task → vk_create_card These are the confirmed tool names from the actual MCP API as of v0.1.17. To connect Vibe Kanban with Codex, run the following from your project root: This command adds the vibe-kanban MCP server config to ~/.codex/config.toml . Hook-based auto-looping is not default Codex behavior, so retry/loop management is handled via board card progress states or a higher-level orchestrator. v0.1.17 actual UI structure : Vibe...