CodeHerderSearch⌘KRequest access →

Alternatives · Vibe Kanban

Migrating from Vibe Kanban

An open-source, worktree-isolated kanban board for running several coding agents on one machine, until Bloop wound the company down.

What happened

April 10, 2026

Bloop, the company behind Vibe Kanban, announced on April 10, 2026 that it was shutting down. The Apache-licensed project didn't disappear with it: it's now maintained by the community rather than a company with a roadmap and a support line.

What Vibe Kanban got right

  • Zero-friction local setup: clone it, run it, start a board.
  • Git-worktree isolation done well, so two agents never collided on the same branch.
  • Free and open source, with no seat count to argue about.

What carries over

The same ideas, different names

Nothing here is a new concept. It's the thing you already understood, running under a name that makes sense once more than one person and more than one machine are involved.

A git worktree per branch, created and torn down by hand
A durable per-task sandbox the platform creates, tracks, and cleans up for you
A kanban column
A workflow stage with a server-enforced gate, so a task can't jump from in-progress to done without whatever check that stage requires
The agent you launched in a terminal tab
A session, tied to a task, running on a device you registered
Your laptop, which had to stay on for the board to mean anything
A device you register once, so the work keeps moving whether or not that one laptop is open

What changes once the board is server-side

  • The board moves off your one machine and onto a multi-tenant workspace, so a teammate sees the same backlog from theirs.
  • Staffing happens server-side: a task finds an agent with the right capability instead of waiting for whoever has the board open.
  • Every task carries its own cost, broken out by stage and by model, not just a running total for the whole board.
  • A task can require a second person's approval before it merges, the kind of separation of duties a single-seat board was never built around.

Your first week

From Vibe Kanban to a merged pull request

  1. 1

    Get started

    Sign in and create a workspace. There's no separate account to set up later for the CLI.

  2. 2

    Follow the quickstart

    Install the ch CLI, connect the repo you were already working in, and file one task end to end.

  3. 3

    Add the machine you already have

    Register it as a device, then check what an agent running on it can reach before handing it real work.

  4. 4

    Learn the workflow stages

    See how a task moves from plan to code to review to merge, and where each gate actually sits.

  5. 5

    Check the numbers, then point it at your agent

    See what a task costs by stage and model, then run the same agent CLI you were already using.

Questions

What people migrating from Vibe Kanban ask

Do I have to give up my own machine?

No. Register the same machine you were already running Vibe Kanban on as a device, and CodeHerder dispatches tasks to it the way you were dispatching them yourself, just with a server keeping track instead of a board open in a browser tab.

Does it run the same agent CLI?

Yes. Claude Code is the default harness, and Codex, Cursor, OpenCode, and Pi all work too, so the agent you were already running under Vibe Kanban keeps running, just launched by CodeHerder instead of a click on a card.

What happens to my existing Vibe Kanban board?

Nothing forces you to migrate it wholesale. Bring over the repos and the tasks still in flight, and let finished work stay finished. There's no import tool that has to run first.

What does it cost per task?

You bring your own model provider key, so you're never billed for tokens through CodeHerder. The platform itself is metered on concurrent agents; see the pricing and calculator pages for real numbers.

Sources

Verified against Vibe Kanban's own published notice as of 2026-08-08.

  • Vibe Kanban shutdown notice
CodeHerder

Round up your herd.

Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close