Migration guide
Vibe Kanban after the shutdown: a migration guide
Updated November 17, 20268 min read
Vibe Kanban, the open source board for handing tasks to coding agents, lost the company behind it in April 2026. Its maker, bloop, shut down and the project became community maintained and local only. Your local setup keeps working, but the cloud features are gone and future fixes depend on volunteers. This guide covers exactly what changed, what to save, and where to move your work.
What bloop announced on April 10, 2026
Is Vibe Kanban shutting down?
The company is, the app is not. bloop announced on April 10, 2026 that it was closing. It said Vibe Kanban "will live on, open source and community maintained." The hosted remote services (kanban issues, comments, projects and organisations) stayed up for 30 days and were then removed. Local workspaces keep working. The GitHub page now carries a notice that Vibe Kanban is sunsetting.
bloop also cancelled subscriptions and refunded invoices paid in the 30 days before the announcement. Before the remote services ended, it added a data export feature to the latest release so people could take their data with them.
In practice, that leaves two kinds of user. If you only ever ran Vibe Kanban on your own computer with npx vibe-kanban, nothing broke on the day. If you used the hosted version to share boards with a team, the shared part is gone and you need a new home for it.
Vibe Kanban today: what you lose and what you keep
What you keep
- The app itself, free under the Apache-2.0 licence
- Local workspaces: each still gets its own branch, terminal and dev server
- Support for many agents, including Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR and Qwen Code
- Diff review with inline comments, the built-in preview browser and pull requests
- Your agents and subscriptions, which never depended on bloop
What you lose
- Shared team boards, comments, projects and organisations from the hosted service
- A company paid to fix bugs and keep up with agent updates
- Confidence that a new agent version will keep working with it
- Any paid plan, since subscriptions were cancelled
The biggest long-term risk is the second item on the right. Coding agents change often. When Claude Code or Codex changes how it starts or what it prints, a tool that wraps it needs an update. With no company behind it, those updates now depend on how active the community is.
Checklist for moving your tasks out
Work through this list once, even if you plan to keep Vibe Kanban for a while. It means nothing is stranded if it stops working after a future agent update.
- Update to the latest release and use its export option to save your data while you can.
- Write down every open card: its title, what "done" looks like, and any notes or links.
- For each workspace with unfinished work, open its diff and decide: merge it, finish it, or throw it away.
- Merge or delete old branches so your project history is tidy before you switch tools.
- Copy any agent instructions you kept in Vibe Kanban into your project's notes file (CLAUDE.md for Claude Code, AGENTS.md for Codex).
- Check your dev server settings, such as ports and start commands, and note them down for the new tool.
- Pick your next tool and set it up on one small project first.
- Move the remaining cards over and start one agent per card.
- Keep the old install around for a week in case you missed something, then remove it.
If you used Vibe Kanban to open pull requests on GitHub, those pull requests live on GitHub, not in Vibe Kanban, so they are safe.
Vibe Kanban alternatives, mapped feature by feature
No single tool copies Vibe Kanban exactly. This table shows how each option covers the parts people relied on most. Details are as of November 2026.
| Vibe Kanban feature | VibeCodingDeck | Conductor | Claude Squad | Claude desktop app |
|---|---|---|---|---|
| Task board | To-do board and notes per project | No board; list of workspaces | No board; list of sessions | No board; list of sessions |
| Separate branch per task | Optional safe copy (worktree) per agent | Worktree and branch per workspace | Worktree and branch per session | Optional worktree per session |
| Many agent types | 8: Claude Code, Codex, Gemini, Copilot, Antigravity, Grok, Qwen, Kimi | Claude Code, Codex, Cursor, OpenCode | Claude Code, Codex, Gemini, Aider and others | Claude Code only |
| Diff review | Review then merge | Diff viewer and Checks tab | Diff tab | Built in |
| Live preview | Your app's preview inside the pane | Not stated | No | Not stated |
| Pull requests | Not a listed feature | Yes | Commit and push branch | Not stated |
| Platforms | Windows 10/11, Apple-silicon Mac | Mac | Mac, Linux, Windows via WSL | Mac, Windows, Linux beta |
| Cost | $29 a month or $249 a year | See conductor.build | Free (AGPL-3.0) | Included with Claude plans |
Reading the table
If the board was the main draw, VibeCodingDeck is the only one here with a task board per project. It also has Plans in batches: you drop in a plan, each batch goes to one agent, later batches wait for the ones they depend on, and every summary lands in one Results view. That covers the "plan the cards, then work them" habit. Opening pull requests is not one of its listed features, so you would do that step yourself on GitHub. See Claude Code kanban for how the board works.
If isolated workspaces and pull requests mattered most, Conductor is the closest match on a Mac. Read our Conductor alternatives page for how it compares on Windows.
If you want free and open source, Claude Squad gives you a branch per session and a diff view in the terminal, though you trade the board for a list. On Windows it needs WSL; our Claude Squad page explains the setup.
If you only use Claude Code, the Claude desktop app is already in your plan. Press Ctrl+N for a new session and switch on Worktree first, and each session gets its own copy. There is no board, so keep your card list in a notes file or a simple to-do app next to it.
Why a kanban for coding agents still makes sense
The most useful thing Vibe Kanban taught is a habit you can take to any tool: split work into small cards, give each card to one agent in its own copy of the project, and review before you merge. This keeps agents from overwriting each other. It also lets you throw away a bad attempt without losing anything else.
- Small cards win. "Add a password reset email" is a good card. "Build the account system" is five cards.
- One agent per card. Two agents on the same files at the same time cause messy merges.
- Write what done looks like. An agent finishes faster when it knows how its work will be checked.
- Review before merging. Run the app and click through the change, even if you don't read the code.
For more on splitting work across agents, see AI agent orchestration and our guide to agentic coding.
If you stay on Vibe Kanban for now
Staying is a fair choice. The app still runs, the code is open, and nothing forces you off it today. A few habits make staying safer:
- Know which version works for you. When you find a version that runs well with your agents, note its number. You can start a specific version with npx by adding it after an @ sign, for example
npx vibe-kanban@followed by the version number. - Update your agents with care. If Claude Code or Codex gets a big update and Vibe Kanban starts acting oddly, the mismatch is the likely cause. Test agent updates on a spare project first.
- Watch the GitHub page. Community fixes and any new roadmap will show up there first.
- Keep the exit ready. Finish the checklist above anyway, so a switch takes an hour instead of a weekend if you ever need it.
One more point on cost. Vibe Kanban itself is free, but every card still spends your AI plan. Moving to another board doesn't change that, because the agents and their limits stay the same. What a new tool can change is how easily you see that spending. A board that shows usage per account helps you stop before a limit cuts a card off halfway.
If you are comfortable with code, you can also help. Community projects live on bug reports and small fixes, and the project is under Apache-2.0, so you are free to change it for your own use.
Your first week after the switch
Moving boards is easy. Getting back to the same speed takes a few days. This plan keeps the change calm:
- Day 1: install the new tool and run one card on a test project from start to merge. Learn where the diff, the preview and the merge button live.
- Day 2: move your real project in and run two cards at once. Check that each one got its own copy of the code.
- Day 3: bring over the rest of your open cards. Turn on whatever alerts the tool has, so you notice when an agent is waiting.
- Day 4: try a longer plan split into steps. In VibeCodingDeck that is Plans in batches; in other tools, start the later cards only once the earlier ones are merged.
- Day 5: look back at what slowed you down and fix it, whether that's a missing note in CLAUDE.md, a port clash or a card that was too big.
Running more agents also means using your AI plan faster. If you start running out, our Claude Code pricing guide explains what each plan gives you, and running several Claude Code agents covers how to share work without wasting usage.
What Vibe Kanban users ask next
Does Vibe Kanban still work?
+
Yes, locally. bloop said local workspaces continue to function. Only the hosted remote services were removed, 30 days after the April 10, 2026 announcement.
Who made Vibe Kanban?
+
bloop, a company that closed in April 2026. The project now lives on GitHub as open source under Apache-2.0, maintained by the community.
Is there a Vibe Kanban alternative for Windows?
+
Yes. VibeCodingDeck runs natively on Windows 10/11 with a task board per project and up to 12 agents in a grid. The Claude desktop app also runs on Windows if you only use Claude Code.
Sources
Run up to 12 AI coding agents in one window.
Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.
Get startedKeep reading
Task boards
Claude Code kanban: a real task board for AI agents, column by column
Explainer
AI agent orchestration for coding: the words, the patterns and a worked example
Mac and Windows
Conductor app on Mac, and the same idea on Windows
Explainer
Agentic coding, explained in plain English
Parallel agents
How to run multiple Claude Code agents at once: four ways, easiest last