Vibe Kanban alternatives: where to run your agents from a board now

What happened to Vibe Kanban

bloop said most users were on free plans and it couldn't find a business model it wanted to pursue. Remote services stayed up for 30 days after the announcement, then Vibe Kanban moved to a fully local architecture; project pages now lead to a data export. Refunds went out for invoices paid in the previous 30 days.

• Still works: npx vibe-kanban starts the local app, and local workspaces keep functioning. The code stays open source under Apache 2.0 and is community maintained.
• Gone: the hosted kanban issues, comments, projects and organisations that teams shared.
• Slowing down: there has been no release since v0.1.44 on April 24, 2026, so new agent versions aren't being picked up.

How to keep your work

1. Export your data

   Open the latest version of the app and use its data export. Project pages now point straight to it.

2. Push every branch you care about

   Each workspace was a git worktree on its own branch. Commit and push the ones you want, so the code lives in your repository rather than in the app.

   # Keep running the local, community-maintained app
   npx vibe-kanban
   
   # Find the worktrees it made, then push the branches you want to keep
   git worktree list
   cd <worktree path>
   git add -A && git commit -m "WIP from Vibe Kanban"
   git push -u origin HEAD

3. Move open issues somewhere shared

   If your team used the hosted board, recreate the open issues in GitHub Issues or in the board of the tool you pick, before anyone forgets what they were.

4. Try one real task in the replacement

   Compare the options below and run one issue from start to pull request before you move everything.

Source: Vibe Kanban's shutdown announcement

Vibe Kanban alternatives compared

Facts from each project's own site or GitHub repository on November 7, 2026.

Which Vibe Kanban alternative fits you

• You want the same app, as it is: keep running the community version locally, and watch the repository for a maintained fork.
• You mostly ran parallel agents and reviewed diffs: Paradev is the closest maintained desktop app, on Mac and Linux. Claude Code's own --worktree flag also covers isolated parallel sessions; see the Claude Code worktree guide.
• You live in the terminal: Claude Squad gives each agent a tmux session and a worktree.
• You want the board itself, for Claude Code only: Kanban Code moves cards between columns as sessions start, wait and open PRs.
• You used the hosted board with a team, or want agents to pick up issues without you: that's Crewmark (below). Conductor was another option, but it's joining Meta and winding down.

Vibe Kanban waited for you to start each card. Crewmark doesn't.

In Vibe Kanban you wrote the issue and then started the agent. Crewmark keeps the board, hosted and shared, and turns a Claude Code, Codex, DeepSeek Harness or OpenCode session into an AI employee that wakes on a heartbeat during working hours and takes the next issue itself, on the subscription you already pay for.

1. Bring your repository and your agent

   Run the setup command in the project. Each employee works in its own session and checkout, much like a Vibe Kanban workspace.

2. Recreate your board

   Add your open issues and assign them to an employee, or leave them unassigned for whoever is free.

3. Let the heartbeat start the work

   Every 15, 30 or 60 minutes the employee takes the next issue, comments as it goes and messages you when it needs a decision. See what an AI employee is.

Vibe Kanban shutdown FAQ