Compare · Deep dive
dev-mux vs Vibe Kanban
Vibe Kanban deserved its 27k GitHub stars: a kanban board where each card spawned coding agents in auto-managed worktrees, with status updates and inline diff review. It proved — with a claimed 30,000 active users and 100,000 generated PRs — that people want to orchestrate agents, not babysit terminals. Then Bloop, its company, shut down in April 2026. This page is for the people deciding what to run next.
What Vibe Kanban was (and is)
npx vibe-kanban ran a local server and web UI; agents executed
locally in managed git worktrees, cards tracked their progress, and you reviewed
diffs with inline comments — vendor-agnostic across Claude Code, Codex, and friends,
with MCP support. Bloop's shutdown note was candid: the vast majority of users were
free, and no business model emerged. Paid plans were refunded; the Apache-2.0 repo
remains, with no visible maintenance cadence since.
At a glance
As of July 31, 2026. If something here is stale, tell us.
| dev-mux | Vibe Kanban | |
|---|---|---|
| What it is | Self-hosted fleet control plane | Local kanban UI for parallel agents |
| Status | Live product, company behind it | Company dead (Apr 2026); repo stale since |
| Scope | Every machine, repo, and agent — one live map | One machine, one browser tab |
| Sessions | tmux-native, persistent, attach from anywhere | Its own execution model; no attach-anywhere |
| Attention | Hook-level signals + push, fleet-wide | Board-status based, in the tab |
| Away from keyboard | iOS, TUI, browser, glasses, Telegram | — |
| Support | A company you can email | Community volunteers, no cadence |
| Price | Solo $25/mo · Team $100/mo | $0 (OSS only; paid plans refunded at shutdown) |
What Vibe Kanban got right
- The board metaphor — task cards spawning agents made parallel work legible to non-terminal people; it's still a great UI idea.
- Vendor agnosticism — switching agent vendors per task was ahead of its time.
- It proved the market — 27k stars and 30k users for “multiplex your agents” is why this whole category exists.
Where dev-mux is a different layer
- Someone maintains it. The uncomfortable core fact: Vibe Kanban's hosted service is gone, its repo hasn't moved since April, and security or agent-CLI breakage lands on you. dev-mux ships weekly with a company behind it.
- Machines, plural. The board ran agents on the box running
npx. dev-mux spans your laptop, VMs, and Pis in one freshness-aware map, over your own tailnet. - Sessions you can grab. dev-mux work lives in tmux — attach from a terminal, the browser cockpit, or an iPhone mid-run. The board's execution model had no equivalent.
- Sustainable on purpose. Bloop's own shutdown note named the failure mode: mostly-free users, no model. dev-mux is paid-only precisely so it's still here next April.
Common questions
Is Vibe Kanban dead?
Bloop shut down April 2026; paid plans were refunded. The Apache-2.0 code still works locally but has had no visible maintenance since.
What is the closest replacement for Vibe Kanban?
For single-machine parallel agents: Sculptor or Conductor. For supervising agents across machines with live status — the direction the board gestured at — that's dev-mux.
Can dev-mux import my Vibe Kanban setup?
Nothing to import — different execution models. But dev-mux adopts plain tmux sessions, so moving is 'run agents in tmux, add the box as a spoke,' not a migration project.
The board proved the demand. The fleet is what comes after.
Get early accessWritten 2026-07-31 against the Vibe Kanban repo, Bloop's shutdown note, and archived product pages. Vibe Kanban is a trademark of its owners; no affiliation or endorsement implied. Corrections welcome.