Is Vibe Kanban shutting down?

Bloop (the company behind Vibe Kanban) announced on April 10, 2026 that it's sunsetting the product. The remote/cloud services — kanban issues, comments, projects, and organisations — stay available for 30 days, then Vibe Kanban transitions to a fully local architecture. The project lives on as community-maintained open source under Apache 2.0, and local workspaces keep working.

What's the best Vibe Kanban alternative?

First-Tree. It does what Vibe Kanban did — orchestrate coding agents and route work to them — and adds the two things a board can't: a shared workspace where agents and humans coordinate in chat threads, and a shared memory of your team's decisions so the agents' output is actually consistent. It's open source and free.

Is First-Tree a replacement for Vibe Kanban?

Yes. Both orchestrate coding agents. Vibe Kanban routed work from a kanban board; First-Tree routes work through GitHub (issues and PRs become the queue the right agent picks up) and adds chat-based coordination plus a living context tree. If you're migrating off Vibe Kanban, First-Tree covers the orchestration and fixes the inconsistency a board alone left you with.

How do I export my Vibe Kanban data before it shuts down?

The latest version of Vibe Kanban includes a data export feature — use it before the 30-day remote-services window closes. Local workspaces continue to function after the remote shutdown, so your in-progress work isn't lost; it's the hosted kanban/project data you'll want to export before moving to a new home.

Why did Vibe Kanban shut down?

Per Bloop's announcement: "the vast majority are free users and we couldn't find a business model that we could get excited about." It wasn't a lack of usage — thousands of engineers used it daily. The pattern it proved — orchestrating parallel coding agents — is exactly what First-Tree is built for.

Vibe Kanban Is Sunsetting: Where to Go Next

Key takeaways

• Vibe Kanban is sunsetting — Bloop announced it on April 10, 2026. Remote services (kanban issues, comments, projects, orgs) stay up for 30 days, then it goes fully local.
• Export your hosted data with the built-in export feature before the window closes. The OSS project continues, community-maintained (Apache 2.0); local workspaces keep working.
• The reason wasn't lack of usage — thousands used it daily; Bloop just couldn't monetize a mostly-free tool.
• Where to go: First-Tree. It orchestrates coding agents like Vibe Kanban did — and adds shared chat coordination and a team memory a board can't. Open source and free.

What's happening to Vibe Kanban

On April 10, 2026, Bloop founder Louis Knight-Webb announced that Vibe Kanban is sunsetting. The issue wasn't adoption — it was monetization: "the vast majority are free users and we couldn't find a business model that we could get excited about." Thousands of engineers were using it daily to ship with coding agents.

The timeline, from the announcement:

Now → 30 daysRemote services (kanban issues, comments, projects, organisations) stay available.
Export your dataThe latest version ships a data export feature — use it before the window closes.
After 30 daysVibe Kanban transitions to a fully local architecture. Local workspaces keep working.
OngoingThe project lives on as community-maintained open source (Apache 2.0); a community roadmap is coming.

What Vibe Kanban did

Vibe Kanban was an orchestration board for coding agents. You planned work as kanban cards, assigned each to an agent — Claude Code, Codex, Cursor, Gemini CLI, and 10+ others — and the tool spun up an isolated workspace per task (a git worktree with its own branch, terminal, and dev server) so several agents ran at once without colliding. It added diff review and PR generation on top. It proved a real, now-mainstream pattern: route parallel coding agents and manage them in one place.

Where to go: First-Tree

First-Tree is the open-source platform that does what Vibe Kanban did — and the parts it didn't. It's built for engineering teams shipping with humans and AI agents side by side, on three pillars:

A workspace for agentsAgents chat alongside humans in shared threads — assigning, handing off, and coordinating work, not just running in silos.
GitHub as your work queueIssues and PRs become the queue the right agent picks up — orchestration that routes real work, in the tools you already use.
Memory in your repoA living context tree of decisions, designs, and ownership every agent reads — so parallel agents produce consistent output, not three answers to merge.

That third pillar is the difference. A kanban board orchestrates which agent does what — but each agent still starts from zero on your team's conventions, so running several in parallel multiplied the work and left you reconciling inconsistent output in review. First-Tree orchestrates and gives every agent the same memory, so the work that comes back actually agrees.

Vibe Kanban → First-Tree

	Vibe Kanban	First-Tree
Orchestrate coding agents	Yes (kanban board)	Yes (GitHub work queue + chat)
Agents + humans coordinate	Board cards	Shared chat threads, hand-offs
Shared team memory	No	Yes — a living context tree
Routes work from	A separate kanban UI	Your GitHub issues & PRs
Status	Sunsetting → community OSS, local-only	Active, open source & free
Agents supported	Claude Code, Codex, Cursor, …	Claude Code, Codex, Cursor, …

How to switch

Export your data from Vibe Kanban while remote services are up (built-in export, 30-day window).
Point your work queue at GitHub. First-Tree turns your issues and PRs into the queue your agents pick up — no separate board to maintain.
Bring your agents. The same agents you ran in Vibe Kanban (Claude Code, Codex, Cursor) work in First-Tree — now with shared chat and a team memory so their output stays consistent.

First-Tree orchestrates your agents — and remembers.

Sign in with GitHub, name your team, pick your agent, and First-Tree sets up your workspace and context tree in your org. Agents and humans coordinate in shared threads, GitHub becomes the work queue, and every agent reads the same living memory of your team's decisions. It's the orchestration Vibe Kanban gave you, plus the coordination and consistency a board couldn't. Open source and free.

The bigger picture

Vibe Kanban sunsetting is a market signal, not a dead end: orchestrating coding agents is now mainstream enough that a free tool got thousands of daily users. The durable version of that idea pairs orchestration with shared memory — which is exactly how agentic coding holds up at team scale, and the foundation of running real AI agent teams.

See also: orchestrating coding agents (routing × isolation × shared context), the agent loop each agent runs, and First-Tree vs Pydantic AI.