Platform Support Status (Current)

Platform	Current Support	Requirements
Claude	Native MCP integration	Register in mcpServers
Codex	MCP script integration	scripts/mcp-setup.sh --codex or equivalent config
Gemini	MCP registration	mcpServers/bridge configuration
OpenCode	MCP/bridge integration	omx/ohmg or equivalent setup

Whether this skill alone is sufficient:

• Claude/Gemini: Yes
• Codex: Yes (requires script-based setup)
• OpenCode: Yes (via orchestration)

Vibe Kanban — AI Agent Kanban Board

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.

When to use this skill

• When breaking an epic into independent tasks for parallel agent assignment
• When you want to visually track the status of ongoing AI work
• When you want to review agent results as diffs/logs in the UI and retry them
• When combining GitHub PR-based team collaboration with AI agent work

---

Prerequisites

# Node.js 18+ required
node --version

# Complete agent authentication beforehand
claude --version    # Set ANTHROPIC_API_KEY
codex --version     # Set OPENAI_API_KEY (optional)
gemini --version    # Set GOOGLE_API_KEY (optional)
opencode --version  # No separate setup needed (GUI-based)

Verified versions (as of 2026-02-22)

• vibe-kanban: v0.1.17
• claude (Claude Code): 2.1.50
• codex: 0.104.0
• gemini: 0.29.5
• opencode: 1.2.10

---

Installation & Running

npx (fastest)

# Run immediately (no installation needed)
npx vibe-kanban

# Specify port (default port 3000)
npx vibe-kanban --port 3001

# Specify port and environment variable together
PORT=3001 npx vibe-kanban --port 3001

# Use wrapper script
bash scripts/vibe-kanban-start.sh

Browser opens http://localhost:3000 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 http://localhost:3001.

Normal startup log:

Starting vibe-kanban v0.1.17...
No user profiles.json found, using defaults only
Starting PR monitoring service with interval 60s
Remote client initialized with URL: https://api.vibekanban.com
Main server on :3001, Preview proxy on :XXXXX
Opening browser...

Clone + dev mode

git clone https://github.com/BloopAI/vibe-kanban.git
cd vibe-kanban
pnpm i
pnpm run dev

---

Environment Variables

Variable	Description	Default
PORT	Server port	3000
HOST	Server host	127.0.0.1
VIBE_KANBAN_REMOTE	Allow remote connections	false
VK_ALLOWED_ORIGINS	CORS allowed origins	Not set
DISABLE_WORKTREE_CLEANUP	Disable worktree cleanup	Not set
ANTHROPIC_API_KEY	For Claude Code agent	—
OPENAI_API_KEY	For Codex/GPT agent	—
GOOGLE_API_KEY	For Gemini agent	—

Set in .env file before starting the server.

API key location per agent (Settings → Agents → Environment variables)

• Claude Code: ANTHROPIC_API_KEY
• Codex: OPENAI_API_KEY
• Gemini: GOOGLE_API_KEY
• Opencode: No separate setup needed (built-in auth)

---

MCP Configuration

Vibe Kanban runs as an MCP (Model Context Protocol) server, letting agents control the board directly.

Claude Code MCP Setup

~/.claude/settings.json or project .mcp.json:

{
  "mcpServers": {
    "vibe-kanban": {
      "command": "npx",
      "args": ["vibe-kanban", "--mcp"],
      "env": {
        "MCP_HOST": "127.0.0.1",
        "MCP_PORT": "3001"
      }
    }
  }
}

OpenCode MCP Setup

Add to ~/.config/opencode/opencode.json:

{
  "mcp": {
    "vibe-kanban": {
      "command": "npx",
      "args": ["vibe-kanban", "--mcp"],
      "env": {
        "MCP_HOST": "127.0.0.1",
        "MCP_PORT": "3001"
      }
    }
  }
}

After restarting, vk_* tools are available directly in your OpenCode session.

MCP Tool List

Tool	Description
vk_list_cards	List all cards (workspaces)
vk_create_card	Create a new card
vk_move_card	Change card status
vk_get_diff	Get card diff
vk_retry_card	Re-run a card

⚠️ 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.

Codex MCP Integration

To connect Vibe Kanban with Codex, run the following from your project root:

bash scripts/mcp-setup.sh --codex

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.

---

Workspace → Parallel Agents → PR Workflow

v0.1.17 actual UI structure: Vibe Kanban is a Kanban board, but the actual unit of work is a Workspace. Each workspace handles one task independently.

1. Start the server

# Default run
npx vibe-kanban
# → http://localhost:3000

# Port conflict (e.g., Next.js)
PORT=3001 npx vibe-kanban --port 3001
# → http://localhost:3001

2. (Optional) Review epic plan with planno

Review the implementation plan for this feature with planno

planno (plannotator) is an independent skill — usable without Vibe Kanban.

3. Create a Workspace

1. Open the UI → click "+ Create Workspace" or the + button in the left sidebar
2. Which repositories? screen:
   • Browse → select a git repo from the filesystem (manual path entry supported)
   • Recent → previously used repos
   • Select a repo, then choose a branch (default: main)
   • Click Continue
3. What would you like to work on? screen:
   • Select an agent (Opencode, Claude Code, Codex, Gemini, Amp, Qwen Code, Copilot, Droid, Cursor Agent)
   • Enter a task description (Markdown supported)
   • Select a mode (Default, Build, etc.)
   • Click Create

4. Automatic agent execution

When a workspace is created:

• A vk/<hash>-<slug> branch is created automatically (e.g., vk/3816-add-a-comment-to)
• A git worktree is created automatically (fully isolated per agent)
• The selected agent CLI runs with log streaming

Workspace states:

• Running: Agent is executing (left sidebar)
• Idle: Waiting
• Needs Attention: Agent finished or needs input

5. Review results

• Changes panel: View file diffs
• Logs panel: Agent execution logs
• Preview panel: Web app preview
• Terminal: Run commands directly
• Notes: Write notes

6. Create PR & finish

• Workspace detail → "Open pull request" button
• PR merge → workspace moves to Archive
• Worktree cleaned up automatically

---

Git Worktree Isolation Structure

Workspace directory (configurable in Settings → General → Workspace Directory):

~/.vibe-kanban-workspaces/          ← default location (under home directory)
├── <workspace-uuid-1>/             ← workspace 1 isolated environment
├── <workspace-uuid-2>/             ← workspace 2 isolated environment
└── <workspace-uuid-3>/             ← workspace 3 isolated environment

Branch naming (configurable in Settings → General → Git → Branch Prefix):

vk/<4-char ID>-<task-slug>
e.g.: vk/3816-add-a-comment-to-readme

Internal behavior:

git worktree add <workspace-dir> -b vk/<hash>-<task-slug> main
<agent-cli> -p "<task-description>" --cwd <workspace-dir>

Recommended .gitignore entries:

.vibe-kanban-workspaces/
.vibe-kanban/

---

Remote Deployment

Docker

# Official image
docker run -p 3000:3000 vibekanban/vibe-kanban

# Pass environment variables
docker run -p 3000:3000 \
  -e ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY \
  -e VK_ALLOWED_ORIGINS=https://vk.example.com \
  vibekanban/vibe-kanban

Reverse Proxy (Nginx/Caddy)

# CORS must be allowed
VK_ALLOWED_ORIGINS=https://vk.example.com

# Or multiple origins
VK_ALLOWED_ORIGINS=https://a.example.com,https://b.example.com

SSH Remote Access

Integrates with VSCode Remote-SSH:

vscode://vscode-remote/ssh-remote+user@host/path/to/.vk/trees/<task-slug>

---

Troubleshooting

Worktree conflicts / orphaned worktrees

# Clean up orphaned worktrees
git worktree prune

# List current worktrees
git worktree list

# Force remove a specific worktree
git worktree remove .vk/trees/<slug> --force

403 Forbidden (CORS error)

# CORS config required for remote access
VK_ALLOWED_ORIGINS=https://your-domain.com npx vibe-kanban

Agent won't start

# Test CLI directly
claude --version
codex --version

# Check API keys
echo $ANTHROPIC_API_KEY
echo $OPENAI_API_KEY

Port conflict

# Use a different port
npx vibe-kanban --port 3001

# Or use environment variable
PORT=3001 npx vibe-kanban

SQLite lock error

# Disable worktree cleanup and restart
DISABLE_WORKTREE_CLEANUP=1 npx vibe-kanban

---

UI vs CLI Decision Guide

Situation	Mode
Shared team board, visual progress tracking	UI (npx vibe-kanban)
CI/CD pipeline, script automation	CLI (scripts/pipeline.sh)
Quick local experiments	CLI (scripts/conductor.sh)
Browser diff/log review	UI

---

Supported Agents (verified v0.1.17)

Configure each agent in Settings → Agents:

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

• ›Claude Desktop or compatible AI client
• ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
• ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
• ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

1. 1Install product management skill
2. 2Start with user story generation for known feature
3. 3Progress to competitive analysis: research 2-3 competitors
4. 4Use for roadmap prioritization: apply RICE/ICE scoring
5. 5Draft stakeholder communications and refine based on feedback
6. 6Build template library for recurring PM tasks
7. 7Share effective prompts with product team

Common Pitfalls

• ⚠Not validating competitive research—verify facts before sharing
• ⚠Accepting user stories without involving engineering team
• ⚠Over-relying on frameworks without qualitative judgment
• ⚠Not customizing outputs to company culture and communication style
• ⚠Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

• +Validate research and competitive analysis with real data
• +Collaborate with engineering when generating technical requirements
• +Customize frameworks and templates to your company context
• +Use skill for first drafts, refine with stakeholder input
• +Document successful prompt patterns for PM tasks
• +Combine AI efficiency with human judgment and intuition

✗ Don't

• −Don't publish competitive analysis without fact-checking
• −Don't finalize user stories without engineering review
• −Don't make prioritization decisions solely on AI scoring
• −Don't skip customer validation of generated requirements
• −Don't ignore company-specific context and culture

💡 Pro Tips

• ★Provide context: company goals, constraints, customer feedback
• ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
• ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
• ★Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

1. 1Basic: user stories, feature specs, status updates
2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
3. 3Advanced: product strategy, go-to-market planning, OKR setting
4. 4Expert: product vision, market positioning, business model innovation

Related Skills

web-accessibility

55

supercent-io/skills-template

Productivitysame repo

grill-me

356

mattpocock/skills

Productivitysame category

premortem

194

parcadei/continuous-claude-v3

Productivitysame category

deslop

113

cursor/plugins

Productivitysame category

framer-motion

96

pproenca/dot-skills

Productivitysame category

write-a-prd

88

mattpocock/skills

Productivitysame category

Reviews

4.4★★★★★70 reviews

• C

  Charlotte White★★★★★Dec 28, 2024

  vibe-kanban has been reliable in day-to-day use. Documentation quality is above average for community skills.

• C

  Chaitanya Patil★★★★★Dec 24, 2024

  I recommend vibe-kanban for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

• E

  Emma Diallo★★★★★Dec 16, 2024

  Registry listing for vibe-kanban matched our evaluation — installs cleanly and behaves as described in the markdown.

• A

  Alexander Liu★★★★★Dec 16, 2024

  Keeps context tight: vibe-kanban is the kind of skill you can hand to a new teammate without a long onboarding doc.

• K

  Kwame Verma★★★★★Dec 16, 2024

  vibe-kanban reduced setup friction for our internal harness; good balance of opinion and flexibility.

• E

  Emma Gill★★★★★Dec 8, 2024

  I recommend vibe-kanban for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

• E

  Emma Rao★★★★★Nov 27, 2024

  vibe-kanban fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

• J

  James Lopez★★★★★Nov 19, 2024

  Useful defaults in vibe-kanban — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

• E

  Emma Patel★★★★★Nov 19, 2024

  Solid pick for teams standardizing on skills: vibe-kanban is focused, and the summary matches what you get after install.

• P

  Piyush G★★★★★Nov 15, 2024

  vibe-kanban fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 70

prev1 / 7next

Discussion

Comments — not star reviews

Post comment

• No comments yet — start the thread.

sharebookmark

Agent	Command	API Key
Opencode	opencode	Built-in (default)