Vibe Kanban's company shut down. Here are the alternatives for agent users

What happened to Vibe Kanban

Vibe Kanban was a task board built by a company called Bloop. Each card on the board launched a coding agent (an AI program that writes and edits code, such as Claude Code, Codex, Gemini CLI or Amp) in its own isolated copy of a project, called a git worktree. A browser interface let you look over the changes the agent made.

On 10 April 2026, Bloop announced it was closing. As dev.to reported in a guide on alternatives, the project's repository now says openly that the tool is being wound down.

The software itself did not vanish. The code remains open source under the Apache-2.0 license, and volunteer maintainers still add to it. What disappeared was the company's hosted side.

What survived and what didn't

The online services kept running for 30 days after the announcement. After that, the app worked only on your own computer. Anything that depended on Bloop's servers was dropped: boards shared between people, comments, projects and organisation accounts. Bloop did offer a way to export your data.

Development has also slowed. The newest version the guide names is v0.1.44, dated 24 April 2026. The guide notes that slower fixes are the main risk for people who stay, because the command-line agents the board talks to keep changing.

So the right response depends on how you used it. If you worked alone on one machine, little has changed. If your team looked at the same board, that board no longer exists.

The alternatives, in plain terms

The guide's table covers five replacements. All details below are what each tool's own site or repository says, as of November 2026.

• Claude Squad is for people who like the terminal. It puts each agent in its own tmux session (a way to keep several terminal windows running) and its own worktree. It has no board, uses the AGPL-3.0 license and runs on macOS and Linux, with Windows only through WSL, a Linux layer for Windows.
• Nimbalyst, previously called Crystal, is an open-source desktop app for macOS, Windows and Linux. It handles Claude Code, Codex and OpenCode, includes a phone companion, and costs nothing for individual users.
• Conductor is a closed-source Mac-only app for Claude Code, Codex and Cursor. It gives each agent a separate workspace and can turn the result into a pull request, a proposal to merge code into a project.
• Paradev, formerly Superset, runs several command-line agents side by side on the desktop. Its source is viewable, but the Elastic License 2.0 makes it source-available rather than truly open source.
• AgentVera supports 18 command-line agents on macOS, Windows and Linux and is the only option here built around a shared team board.

A note on who wrote the guide

The guide first appeared on the AgentVera blog, and its authors say plainly that they make AgentVera. That does not make the comparison wrong, but it does mean you should read the AgentVera section as a sales pitch with useful detail, and check claims on each tool's own site, as the authors themselves advise.

On the board feature, AgentVera works like this: you send a card to an agent running on your own computer, the card moves to "In progress", and the agent's final reply comes back as a comment. Only cards, comments and assignments go to the cloud, while your project folder stays local. It uses the logins you already have for the agent tools, so no API key is needed.

The trade-offs are stated too. AgentVera is closed source, and the board requires a paid plan: Pro allows 10 boards and Team allows unlimited ones. The terminal grid, worktrees and all 18 agents are on the free plan.

Moving off without losing work

The guide's migration advice is short. First, pull whatever you need from the old cloud boards if you still hold an export, because the tool no longer syncs them. Second, finish or merge any open worktrees. They are ordinary git worktrees, so any of the tools above can open them.

Third, keep your existing agent logins, since every tool here drives the same command-line programs you already installed. Finally, rebuild only the cards still in progress and treat finished ones as history.

The lesson goes beyond this one product. The parts of a workflow that lived on someone else's servers were the parts that broke, while the local parts kept working.