A local-only fork of BloopAI/vibe-kanban, kept alive past the upstream sunset.

What this fork is

This repository is a fork of BloopAI/vibe-kanban taken at the pre-sunset cutover. The cutover removed every cloud-dependent feature — authentication, organizations, team collaboration, real-time sync, relay tunnel, analytics, error reporting — leaving a self-contained single-user kanban that runs entirely against a local SQLite database. Everything else (the kanban UI, workspaces, sessions, coding-agent integrations, PR creation, MCP server) still works the same way it did upstream.

If you want the original cloud-enabled product, use BloopAI/vibe-kanban. If you want to keep using vibe-kanban locally now that the upstream hosted service has shut down, you're in the right place.

What's in here

• Single-user local kanban with synthetic identity auto-seeded on first launch (no signup, no login)
• Workspaces, sessions, kanban board, settings — fully functional against a local SQLite database
• 10+ coding agents configurable from the UI: Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR, Qwen Code
• Pull request creation with AI-generated descriptions
• MCP server for programmatic access (vibe-kanban-mcp --mode global)

Install

From a release (recommended)

Download the latest binaries from the releases page, make them executable, and run:

chmod +x server vibe-kanban-mcp
./server                          # starts the UI
./vibe-kanban-mcp --mode global   # optional: stdio MCP for agent integrations

The server prints the URL it bound to (it auto-assigns a free port unless PORT is set) and writes the chosen port to $TMPDIR/vibe-kanban/vibe-kanban.port so other tools can find it.

Only macos-arm64 is published today. For other platforms, build from source.

From source

git clone git@github.com:kcarwileklaviyo/vibe-kanban-local.git
cd vibe-kanban-local
pnpm i
pnpm run build
cargo build --release --bin server --bin vibe-kanban-mcp
./target/release/server

Development

Prerequisites

• Rust (latest stable)
• Node.js (>=20)
• pnpm (>=8)

Additional development tools:

cargo install cargo-watch
cargo install sqlx-cli

Run the dev server

pnpm i
pnpm run dev

This starts the backend (with cargo-watch) and the web app. A blank DB is copied from dev_assets_seed/ on first launch.

Build the web app standalone

cd packages/local-web
pnpm run build

Environment variables

Variable	Type	Default	Description
PORT	Runtime	Auto-assign	Server port (dev: frontend port; backend uses PORT+1)
BACKEND_PORT	Runtime	0 (auto)	Backend port in dev mode (overrides PORT+1)
FRONTEND_PORT	Runtime	3000	Frontend dev server port (overrides PORT)
HOST	Runtime	127.0.0.1	Backend bind address
MCP_HOST	Runtime	HOST	MCP server connection host
MCP_PORT	Runtime	BACKEND_PORT	MCP server connection port
VK_ALLOWED_ORIGINS	Runtime	unset	Comma-separated list of origins permitted to call the backend (set when running behind a reverse proxy on a custom domain)
VK_NO_BROWSER	Runtime	unset	Skip auto-opening the browser on server start (handy for daemon-driven restarts)
DISABLE_WORKTREE_CLEANUP	Runtime	unset	Disable git worktree cleanup (debugging only)

Reverse proxy / custom domain

When running behind a reverse proxy (nginx, Caddy, Traefik, etc.) or on a non-localhost domain, set VK_ALLOWED_ORIGINS to the public origin(s):

VK_ALLOWED_ORIGINS=https://vk.example.com
# or comma-separated for multiple
VK_ALLOWED_ORIGINS=https://vk.example.com,https://vk-staging.example.com

Without this, the backend rejects requests with a 403 because the browser's Origin header won't match the bound host.

Documentation

The original upstream documentation site at vibekanban.com no longer exists. The docs/ directory in this repo carries the parts that still apply post-cutover; sections describing cloud-only features (authentication, organizations, team collaboration, etc.) have been removed.

Diverging from upstream

This fork tracks BloopAI/vibe-kanban at a specific commit; it does not pull future upstream changes. Cherry-picking from upstream is possible but generally requires conflict resolution against the cloud removals. PRs welcome that bring in upstream improvements compatible with the local-only model.