Vibe Kanban Is Sunsetting. What to Look For in a Replacement

2026-07-23

On 10 April 2026, bloop, the company behind Vibe Kanban, announced it was shutting down. In the words of the announcement on the Vibe Kanban blog: "Today we're shutting down bloop, the company behind Vibe Kanban. The project will live on as open source and community maintained." The GitHub README now carries a sunsetting notice.

Vibe Kanban was, for many developers, the first tool that made managing AI coding agents feel like managing work instead of babysitting terminals. Write a task, dispatch it to Claude Code or Codex in an isolated Git worktree, review the diff, raise a PR. Roughly 27,000 GitHub stars say the idea landed.

So this is not a takedown. It is a practical guide for the question thousands of its users now face: the tool at the centre of my agent workflow has no company behind it anymore. What do I actually need from whatever comes next?

What "sunsetting" does and does not mean

First, the facts, because "shut down" gets overstated in both directions:

The code is not gone. Vibe Kanban is Apache-2.0 open source and the repository remains online, now community maintained.
The company is gone. There is no longer a business shipping releases, fixing security issues, or keeping pace with agent CLIs that update weekly.
Company-operated remote services are winding down, with the project moving to a fully local architecture.

You can keep running npx vibe-kanban today. The open question is not availability, it is velocity: coding-agent CLIs are among the fastest-moving software in the industry, and a tool that wraps them needs constant compatibility work. That work now depends on volunteers.

The real lesson is about data, not licences

Here is the uncomfortable part. Vibe Kanban was open source, and open source did exactly what it promises: the code survived the company. But your workflow is not made of code. It is made of tasks, decisions, review history, and context, and all of that lived inside the tool's internal store, behind its web UI.

Open source protects the software. It does not automatically protect your work. The property that actually protects your work is an open format: state stored as plain files you can read, grep, back up, and move without the application that wrote them.

That distinction should drive how you evaluate every tool in this category from now on.

Six criteria for a replacement

Whatever you pick next, the bloop shutdown suggests a checklist:

Data that outlives the tool. Can you open your tasks in a text editor after the vendor disappears? If the answer requires an export feature, the answer is no. Look for boards stored as plain files in an open format.
Local-first, with no company services in the loop. Vibe Kanban's remote services wound down with the company. A tool that runs entirely on your machine, with no account and no server dependency, has nothing to wind down.
Active maintenance you can verify. Check the changelog, not the marketing page. Agent CLIs change weekly; a board that launches them needs a release cadence to match.
Bring-your-own agents. The tool should launch the CLIs you already use, such as Claude Code, Codex, Cursor Agent, aider, Amp, OpenCode, Antigravity, or Goose, rather than binding you to one vendor's model. Your agent choice should survive your board choice, and vice versa.
Durable context, not just dispatch. A prompt in a text box is disposable. Look for tools where the task carries persistent state an agent can be briefed from, and where sessions survive a restart instead of evaporating per run.
Room for the rest of the project. Coding tasks are rarely the whole board. If the tool only understands Git repositories, everything else about the project lives somewhere it cannot see.

Where the field stands

Broadly, replacements split into two shapes.

Orchestrators keep Vibe Kanban's design centre: fan tasks out to parallel agents, isolate runs, review diffs, merge PRs. Several actively maintained tools now compete in that lane, and if your workload is a queue of well-scoped code changes, an orchestrator is the like-for-like swap.

Project managers with embedded agents invert the model: the board is the durable source of truth, and agents are teammates who work from it. That is where Kanban Pro sits. Every ticket is a Markdown file with YAML frontmatter on your own disk. Agents attach through embedded per-ticket terminals that launch real CLIs (Claude Code, OpenAI Codex, Cursor Agent, aider, Amp, OpenCode, Antigravity, Goose), auto-briefed with a generated KP-CONTEXT.md covering the active ticket, its neighbours, the board columns, and the project rules. Sessions persist under .kanban/sessions/ and resume later. It is a free desktop app for macOS and Windows, signed installers from GitHub Releases, no account, and it is actively developed with a public changelog. Its free Early Access passed 4,100 downloads and reached #1 on r/MacApps in July 2026.

Measured against the checklist: tickets are plain files (1), the app is 100% local with no server component (2), releases ship regularly (3), it launches eight agent CLIs natively (4), briefing and session persistence are built in (5), and Board, List, Table, Calendar, Notes, and Gantt views handle the non-coding work (6).

What Kanban Pro deliberately does not do is Vibe Kanban's headline trick: provisioning parallel Git worktrees per task with built-in diff review and PR creation. In Kanban Pro that is the agent's job, not the board's. Tools like Claude Code can create worktrees and raise PRs themselves when asked. If you specifically want board-managed parallel code execution, an orchestrator will fit better, and the two approaches are not mutually exclusive, because Kanban Pro tickets are plain files any executor can read.

For a detailed head-to-head, see Kanban Pro vs Vibe Kanban.

Migrating without ceremony

There is no import lock-in on either side of this move. Vibe Kanban tasks are short, prompt-shaped descriptions; Kanban Pro tickets are small Markdown files whose format is documented in the README generated inside every board folder. Recreate your open tasks as tickets, put the board folder in or beside your repository, and launch your existing CLI from each ticket's embedded terminal. Your agents keep their tools. The board around them becomes files you own.

Frequently Asked Questions

Why is Vibe Kanban sunsetting?

bloop, the company behind Vibe Kanban, announced on 10 April 2026 that it was shutting down. The project was released to the community as Apache-2.0 open source rather than being taken offline, and the GitHub README now carries a sunsetting notice.

Can I keep using Vibe Kanban after the shutdown?

Yes. The code remains on GitHub and runs locally via npx. What changes is maintenance: security fixes and compatibility updates with fast-moving agent CLIs now depend on community volunteers rather than a company with a release schedule.

What should I look for in a Vibe Kanban replacement?

Six things: task data stored as plain files that outlive the tool, a local-first architecture with no company services in the loop, verifiable active maintenance, support for the agent CLIs you already use, durable per-task context with resumable sessions, and support for non-coding work on the same board.

Is Kanban Pro a drop-in replacement for Vibe Kanban?

It replaces the board, not the orchestration style. Kanban Pro is a local-first project manager where every ticket is a Markdown file and agents run in embedded per-ticket terminals with auto-generated briefings. It does not provision parallel Git worktrees or create PRs itself; agent CLIs handle that when asked.

Is Kanban Pro free?

Yes. Kanban Pro is free during Early Access, with no subscription, no account, and no trial expiry, downloaded as signed installers for macOS and Windows from GitHub Releases.

Download Kanban Pro — Free Early Access for Mac & Windows →