How to migrate from Vibe Kanban

Checked against Vibe Kanban's announcement and source code on November 7, 2026. Worktree Kanban is not affiliated with Vibe Kanban or bloop.

Your code is safe: Vibe Kanban's work lives in ordinary git branches and worktrees, so it does not depend on any app. Worktree Kanban cannot import Vibe Kanban's boards automatically, so this guide saves what matters first, then moves open work over by hand. Allow about 30 minutes per repository.

What happened to Vibe Kanban

On April 10, 2026, bloop, the company behind Vibe Kanban, announced it was shutting down. The project's README says Vibe Kanban is sunsetting.
The announcement kept remote services for 30 days. Those services covered cloud kanban issues, comments, projects, and organisations. Paid subscriptions ended.
Local workspaces were announced to keep working, and the project was handed to the community. The repository still received commits in November 2026. Its most recent GitHub release is v0.1.44, from April 24, 2026.

If you only use local workspaces, nothing forces you to move today. The reasons to plan a move are the lack of a company behind the project and the absence of new tagged releases since April.

What carries over

In Vibe Kanban	In Worktree Kanban
Git branches and commits	Stay in your repository, ready to use
Workspaces in progress	Recreate them as tasks based on the existing branch (step 5)
Board, issues, and agent conversations	Not imported. Keep the backup for reference and recreate what is still open
Setup script	Setup script
Copy files	Add `cp` lines to the Setup script
Dev server script	Run script, started by hand from the worktree tab
Cleanup and Archive scripts	Cleanup script, which runs just before a worktree is removed
Agent sign-in	Unchanged: both apps use the CLI on your machine

Check the differences first

Worktree Kanban is not a drop-in replacement, so check these before you start.

You would lose

Some agents. Worktree Kanban runs Claude Code, Codex CLI, Antigravity CLI, Gemini CLI, and Cursor CLI. It does not run GitHub Copilot, Amp, OpenCode, Droid, CCR, or Qwen Code. On Antigravity and Gemini, approving actions on the card and a few other features are not available.
The built-in preview browser. Open your dev server in your normal browser instead.
Workspaces spanning several repositories. Each task belongs to one repository. You can keep up to 3 repositories open as tabs.
Vibe Kanban's own MCP server for managing tasks from an agent.
Team boards. Worktree Kanban keeps its board on one machine. There is no shared cloud board.
The Apache-2.0 license. Worktree Kanban is source-available under FSL-1.1-ALv2, which excludes competing commercial products and services. Each version also becomes available under Apache 2.0 two years after its release.

You would gain

Mac and Windows remote control over an SSH tunnel, with no external server.
Pipelines and competition: chain agents in a flowchart, or have several solve the same task.
Splitting large tasks into subtasks, and scheduled tasks.

Migrate in 6 steps

1. Save your work in git

Run this in each repository to list Vibe Kanban's worktrees and branches. The prefix is vk unless you changed it in Vibe Kanban's settings.

git worktree list
git branch --list 'vk/*'

For each worktree you want to keep, commit anything uncommitted and push the branch. This matters because the default worktree location is a temporary folder.

git -C <worktree-path> status --short
git -C <worktree-path> add -A
git -C <worktree-path> commit -m "WIP: move from Vibe Kanban"
git -C <worktree-path> push -u origin HEAD

2. Export cloud data, if you used it

Open /export in Vibe Kanban. It downloads a zip with issues.csv, projects.csv, users.csv, and optionally attachments. The cloud services were announced to last only 30 days, so this may no longer work. If you did not use cloud projects, skip this step.

3. Back up local data

Copy this folder somewhere safe. It holds the database (db.v2.sqlite), config.json, and profiles.json. It can also hold credentials.json, so keep the copy private and do not commit it.

OS	Folder
Mac	`~/Library/Application Support/ai.bloop.vibe-kanban`
Linux	`~/.local/share/vibe-kanban`
Windows	`%APPDATA%\bloop\vibe-kanban\data`

4. Install Worktree Kanban

Mac / Linux:

curl -fsSL https://raw.githubusercontent.com/kazuya83/worktree-kanban/main/install.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/kazuya83/worktree-kanban/main/install.ps1 | iex

Or download it from Releases. The builds are not signed or notarized, so your OS may warn you the first time. Then open your repository, choose your agents under "Agents to use" in Settings, and add your scripts under "Branches and landing".

5. Move open work

Work that is nearly finished: finish it from the worktree or branch in your terminal, and merge it or open a PR as usual.
Work that needs more agent time: set "Base branch" to the vk/... branch under "Branches and landing", then create a task. Its worktree starts from that branch. The merge target defaults to the same branch, so choose your main branch in the merge dialog if you want to land it directly. Then set "Base branch" back.
Issues not started yet: create tasks by hand. If they are GitHub Issues, use the "Create from a GitHub Issue" tab under "+ New task".

The agent does not see the Vibe Kanban conversation, so write what is done and what is left in the new task.

6. Clean up

Once everything is merged or pushed, remove the old worktrees and any branches you no longer need. git branch -d refuses to delete a branch that is not merged.

git worktree remove <worktree-path>
git branch -d vk/<branch-name>
git worktree prune

If you are unsure, do this later. Keeping both apps for a while does no harm.

Download Worktree Kanban