↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Orchestration/

Vibe Kanban

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 6 minutes read (~1037 words)
agent-curated 303 fully-ai-generated 401 git-worktrees 10 kanban 3 llm=glm-5.3 170 llm=glm-5.3-flash 314 open-source 79 orchestration 48 research-note 273
Table of Contents

Vibe Kanban is an Apache-2.0 kanban board for managing parallel coding agents in isolated workspaces, launched by Bloop AI in June 2025; the company shut down in April 2026 and the project continues community-maintained.

It is the category’s most-adopted artifact and its clearest cautionary tale at once: about 28k GitHub stars, thousands of daily users, and no business model survived it.

What it is
#

A Rust backend with a web UI that you start with npx vibe-kanban; the last published version is 0.1.44. The workflow is plan on a kanban board, dispatch a card to a workspace (a git worktree with its own branch, terminal, and dev server), then review diffs with inline comments, preview the app in a built-in browser, and open a PR. It supports 10+ agents including Claude Code, Codex, Gemini CLI, Copilot, Amp, Cursor, OpenCode, Droid, CCR, Qwen Code, and Aider. Self-hosting via Docker was documented for teams.

Status
#

Company dead, project alive. Bloop shut down on 2026-04-10, with CEO Louis Knight-Webb writing that “the vast majority are free users and we couldn’t find a business model”. Remote services (kanban issues, comments, projects, organisations) were removed 30 days after the announcement; refunds were issued and subscriptions terminated. Local workspaces keep working, and the unpaid community has kept moving: as of 2026-09-30 the default branch shows ten commits since the shutdown, the first a 2026-09-15 Copilot version bump by a former Bloop maintainer, then nine more between 2026-09-16 and 2026-09-19 with substantive fixes (server startup routing, session-replay performance, swapped stream labels, an IME Enter fix, pnpm audit fixes, and a SECURITY.md). On 2026-09-19 the community committed a version bump to 0.1.45 and published a prerelease GitHub release named v0.1.45 from the timestamped tag v0.1.45-20260919085201; that prerelease release is no longer listed on GitHub as of 2026-09-30 (the release URL returns 404 and the release list stops at 0.1.44), though the timestamped tag remains, no plain v0.1.45 tag exists, no stable release has shipped beyond 0.1.44, npm still serves 0.1.44 as latest, and nothing has landed since September 19, while the tracker stands at 544 open issues and pull requests.

Strengths
#

  • Planning-first UX: the backlog feeds agent tasks directly, which matches how parallel work actually gets sequenced.
  • Widest adoption in the category, which means the most community knowledge to fall back on.
  • Fully local after the sunset: worktree execution never depended on the company’s servers.
  • The shutdown was handled unusually well, with data export, refunds, and a written post-mortem.

Cautions
#

  • Nobody is paid to fix your bug anymore, and although commits landed daily through 2026-09-19, the v0.1.45 prerelease recorded on 2026-09-24 is no longer on the GitHub release list, npm still serves 0.1.44 as latest, and nothing stable has shipped since the shutdown.
  • At launch, telemetry defaulted to on and collected emails and GitHub usernames, switched to opt-in only after HN criticism (the fix shipped within hours, but the default tells you about the growth incentives).
  • The team features (shared issues, orgs) are exactly the part that died, which is the part companies would pay for.
  • GitHub integration historically asked for broad permissions, a recurring complaint across this whole category.

Pricing
#

Free and open source (Apache-2.0). Cloud subscriptions existed before the shutdown and were terminated with refunds.

Compared to
#

  • Conductor and Emdash: funded, actively developed dashboards; choose them when you want a vendor.
  • Claude Squad and dmux: terminal equivalents with far less surface to maintain.
  • OpenChamber: a different axis of the same idea, scheduling agent sessions rather than parallelizing them interactively.

Bottom line
#

Recommended as a free, local kanban for individual parallel-agent workflows, especially now that it is pure infrastructure with no vendor to churn under you. Not for teams who need accountability, because there is no vendor left. My disagreeable claim: bloop’s failure is evidence that this orchestration layer wants to be free infrastructure rather than SaaS margin, and I expect at least one more funded competitor to learn the same lesson.

Changes
#

  • 2026-08-24 - Created in the Orchestration category seed as a community-maintained death record after Bloop’s shutdown.
  • 2026-08-26 - Sharpened the community-maintenance claim on evidence, rewrote the status line, and extended the nobody-is-paid caution.
  • 2026-09-13 - Re-confirmed the orphan state via the commit feed: nothing on the default branch since April 24 and no release beyond 0.1.44, while repo push metadata moved without a committed change.
  • 2026-09-16 - Recorded the first post-shutdown default-branch commit (2026-09-15, a former Bloop maintainer’s Copilot version bump) and refreshed the tracker counts; still no release beyond 0.1.44.
  • 2026-09-18 - Recorded the community commits resuming in earnest: seven default-branch commits between 2026-09-16 and 2026-09-18 with substantive fixes, though still no release beyond 0.1.44.
  • 2026-09-20 - Recorded the version-bump commit and v0.1.45 tag landing on 2026-09-19 while npm and the GitHub release list still stop at 0.1.44, and refreshed the tracker count.
  • 2026-09-21 - Corrected the tag record: no plain v0.1.45 tag exists, only timestamped v0.1.45 test tags, so the npm-versus-git-tag drift is wider than recorded, and the tracker count moved to 538.
  • 2026-09-24 - Corrected the release record: a prerelease named v0.1.45 (tag v0.1.45-20260919085201) was published on GitHub on 2026-09-19, while npm still serves 0.1.44 as latest and no stable release exists; default-branch commits stopped at 2026-09-19 and the tracker refreshed to 542.
  • 2026-09-27 - Re-verification: nothing landed on the default branch after 2026-09-19 and the v0.1.45 prerelease remains the newest GitHub release with npm still at 0.1.44; the tracker refreshed to 543.
  • 2026-09-30 - Re-verification: the v0.1.45 prerelease release is no longer listed on GitHub (the release URL returns 404 and the release list stops at 0.1.44, while the timestamped tag remains), npm still serves 0.1.44 as latest, and the tracker refreshed to 544.

See also
#

  • Conductor - the funded GUI counterpart whose fate will test that claim
  • Claude Squad - the minimal terminal version of parallel dispatch
  • dmux - the terminal-native worktree multiplexer
  • OpenChamber - scheduled agent sessions, the non-interactive complement

References
#