What happened to Vibe Kanban?
On April 10, 2026, Bloop, the company behind Vibe Kanban,
announced that it was shutting down. The post says the remote
services (kanban issues, comments, projects and organizations) would stay available for 30 days and then be removed.
Local workspaces would keep working, and Vibe Kanban would continue as an open-source, community-maintained
project.
Two changes in the project's own repository show what that meant for the app. A
data export, added on the day of the announcement,
packages issues, projects and users as CSV files in a ZIP, with attachments as an option (status and assignee are columns in the issues file).
Then pull request #3387, merged on April 24, 2026,
replaced the app's project pages, which showed the kanban board and issues from the hosted service, with an export-only screen.
As of October 2026 the repository is public, Apache-2.0
licensed and not archived, and npx vibe-kanban still starts the local app with its agent workspaces.
If you still have data in Vibe Kanban, export it first.
Local agent runner or shared board: how to choose
Start from who needs to see the work, not from the feature list.
- You work alone, in one repo, and want agents started for you. Use a local runner: Cline Kanban or
the KanBots desktop app if you like a board, Claude Squad if you live in the terminal, or Claude Code agent teams if
every agent is Claude Code.
- A team, several agent clients, or people who do not write code need to follow along. Use a shared
board: Flux if you want it hosted, Paca if you want to host it yourself, or KanBots Cloud if you want to keep
KanBots' desktop runner.
- Both. Run agents locally, each in its own worktree, and have them report to the shared board over
MCP. The runner handles the repository. The board holds the plan, the comments and the review queue.
In Flux, that loop uses a few MCP tools: an agent reads the board with get_board, moves its
card with move_card and reports with add_comment. Flux does not enforce a review step.
Any Write-scope key whose owner is a member, admin or owner can move a card to any column on that board, so a
Review column is a team convention. When you create a
key, you choose whether to include Write scope. More on this setup in
kanban boards for AI agents.
Moving from Vibe Kanban to Flux
- Export from Vibe Kanban first. Download the ZIP of CSV files described above. The export runs through Vibe Kanban's
hosted service; if it doesn't work, check the project's repository.
- Sign up for Flux. A new account starts with a board called Project Board, with the columns
Backlog, Planning, In Progress, Review and Complete, and an API key named Starter Agent with Read and Write scope.
The Free plan includes one board. Rename this one, or upgrade the workspace to Pro for more boards
(see pricing). Delete the sample cards before connecting agents.
- Match the columns to your Vibe Kanban statuses. Rename, add or remove columns so each status in
your export has a home.
- Create the cards. There is no Vibe Kanban importer (Flux imports from Trello only). Create one
card per issue with
POST /api/cards, sending boardId, columnId and
title (plus an optional description). Send a new random UUID in the x-idempotency-key header
for each issue, and reuse it only when retrying that same request, so a retry does not create a duplicate. See the API docs for the full
reference. Or hand the CSV to a connected agent and have it call create_card over MCP.
- Connect your agents. In Settings, open API Keys and create a key for each agent (Read is always on;
add Write for agents that change cards). For Claude Code:
claude mcp add flux --transport http https://flux.umin.ai/api/mcp \
--header "Authorization: Bearer flux_YOUR_API_KEY"
For other clients, see the Cursor and Claude
setup pages, or the Flux MCP server page for the endpoint and tool list.
- Tell agents how to use the board. Put a short section like this in your
CLAUDE.md or
AGENTS.md:
## Flux board
- Work only from the Flux board "Project Board".
- Take the top card in Planning and move it to In Progress.
- Work in your own git worktree and branch.
- When done, add a comment with what changed and the branch name,
then move the card to Review.
- Never move a card to Complete. A person does that after review.
Agents that connect this way use your API key and never take a seat, on any plan. You keep running them as
before, in your worktrees and terminals.
Sources (checked October 18, 2026)
Vibe Kanban, Bloop, Cline, KanBots, Claude Squad, Paca, Anthropic, Claude, Claude Code and the other product names on
this page are trademarks of their respective owners, used here only to identify their products. Flux is not affiliated
with, sponsored by or endorsed by any of them. If anything here is inaccurate or out of date, email [email protected] and
we will review it and correct anything that's wrong.
