Bloop, the company behind Vibe Kanban, shut down on 10 April 2026. The project lives on as open source maintained by its community, but the Kanban board that gave it its name is gone from the app: project pages now only offer to export your data. AgentsRoom is a desktop app built around that same idea, a board where a ticket starts a coding agent.
Write the ticket, drop it in a column, and the agent of that column picks it up with the column's prompt: clarify, plan, code, review, test. Each agent runs its real CLI in its own terminal (Claude, Codex, GitHub Copilot CLI, Cursor and 13 other agent CLIs), on your machine and your own subscriptions, and you follow it from the iOS and Android apps.
여기서 에이전트를 시작하는 칼럼은 In Progress뿐입니다. 다른 칼럼에는 프롬프트가 없습니다. 바로 그 뒤에 QA 칼럼을 추가합니다. In Progress에 놓은 티켓은 AI 코딩 에이전트를 시작하고, 에이전트는 티켓이 요청한 함수를 작성합니다. QA로 옮긴 다른 티켓은 그곳에서 기다리기만 하고, 에이전트는 시작되지 않습니다.
Facts checked on 27 October 2026 against the shutdown announcement and the project's GitHub repository.
On 10 April 2026, Bloop announced it was shutting down. Its words: "The Vibe Kanban project will live on, open source and community maintained." The repository is still public under the Apache 2.0 license, a community release (0.1.45) came out in September 2026 and commits were still landing in October. The roadmap for the community edition was announced but we found no published version of it.
The announcement kept the remote services up for 30 days, then a move to a fully local architecture. Remote issues, comments, projects and organizations were to be removed, subscriptions ended, and invoices paid in the last 30 days were refunded.
Since version 0.1.44 (24 April 2026), opening a project in Vibe Kanban shows "Project functionality has been retired" with an Export data button: kanban, issue and workspace flows are no longer available from the project page. The export is a ZIP with your issues and projects as CSV files.
"Local workspaces will continue to function." A workspace gives an agent a branch, a terminal and a dev server, with diff review, an app preview and pull requests. What you lose is the layer above it: the board where work waited, was sorted and was handed out.
Sources:Vibe Kanban shutdown announcementBloopAI/vibe-kanban on GitHub
Vibe Kanban's promise was to plan with issues and let agents execute them. That is the part that matters when you look for a replacement.
In Vibe Kanban, an issue on the board led to a workspace where the agent worked on its own branch. The workspaces are still there and still good at their job: a branch, a terminal, a dev server, a diff to review and a pull request at the end. The board above them is not: you start each workspace yourself and keep track of the queue somewhere else.
In AgentsRoom, the work starts as a ticket in the backlog. Each column can carry its own prompt and its own agent: drop a ticket in Plan and an agent writes the plan, move it to In Progress and the same agent codes with the plan in its context, move it to In Review and a reviewer agent checks the diff. Tickets can come from GitHub Issues, Jira, Linear, Notion or Azure DevOps.
This compares AgentsRoom with Vibe Kanban as it ships today, after the shutdown. The first rows are where Vibe Kanban wins, the middle ones are shared, the last ones are where AgentsRoom goes further.
| Feature | AgentsRoom | Vibe Kanban |
|---|---|---|
| Open source | ✗ | ✓ |
| Free with no caps | Free plan | ✓ |
| Runs in the browser | ✗ | ✓ |
| Pull request with an AI-written description | Opens the host's PR page | ✓ |
| Visual interface | ✓ | ✓ |
| Agent status (working, waiting, done) | ✓ | ✓ |
| Several repositories and projects | ✓ | ✓ |
| Own branch or worktree per task | Optional | ✓ |
| Diff review with line comments | ✓ | ✓ |
| Built-in browser to preview the app | ✓ | ✓ |
| Model per agent | ✓ | ✓ |
| Notifications when an agent finishes | ✓ | ✓ |
| Kanban board feeding the agents | ✓ | Retired in April 2026 |
| A prompt and an agent per column | ✓ | ✗ |
| Board synced across your devices | ✓ | Retired in April 2026 |
| Agent CLIs supported | 17 | 10 |
| The agent CLI in its own terminal | ✓ | Conversation view |
| Phone access | ✓ | Browser, via the hosted cloud |
| Several accounts per provider | ✓ | ✗ |
| Specialized agent roles (14) | ✓ | ✗ |
| Agent teams (visual workflows) | ✓ | ✗ |
| Shared project memory | ✓ | ✗ |
| Prompt and skill libraries | ✓ | ✗ |
| Scheduled and webhook-triggered runs | ✓ | ✗ |
| Setup time | 30 sec | ~1 min |
Vibe Kanban's workspaces handle one task at a time very well. AgentsRoom is built for the moment a dozen tickets and a dozen agents need to know who does what, and in what order.
Vibe Kanban's board is retired. The AgentsRoom backlog has TODO, In Progress, Pending and Done, plus the columns you add, and since version 1.236.0 any column can carry a prompt and a pinned agent. Moving a card becomes a step of your workflow: clarify, plan, code, review, test.
Every AgentsRoom agent has one of 14 specialized roles, Frontend, Backend, QA, DevOps, Security and others, each with its own instructions, default model and color. In Vibe Kanban, you pick a coding agent and its variant for the workspace; the role is whatever you type.
AgentsRoom draws agent teams on a canvas, where Dev hands over to QA and QA to the reviewer, and saved agents can write to each other whatever CLI each one runs. A Vibe Kanban workspace is one agent on one branch.
AgentsRoom keeps a project memory: decisions, conventions and pitfalls written once and read by every agent of the project, whichever CLI it runs. A new agent starts with what the previous ones learned instead of rediscovering it.
Sign in to several accounts of the same provider and AgentsRoom shows the usage of each. At a usage limit, a quota rule can hand the same conversation to another account, and Claude Code and Codex carry on with their full history.
Vibe Kanban's shared board lived on its hosted cloud, the part that was switched off. AgentsRoom agents run on your machine, the backlog is stored with your account so your other computers and your phone see the same board, and the phone talks to the desktop through an end-to-end encrypted relay.
Watch how AgentsRoom drives several coding agents from a single window, with a backlog, specialized roles and one terminal per agent.
데스크톱 앱, 심플 모드로
휴대폰에서는 데모가 실제 데스크톱 앱을 심플 인터페이스 모드로 실행합니다. 프로젝트 하나, 그 에이전트들, 프롬프트 하나. 전체 조종석은 컴퓨터에서 이용할 수 있습니다.
An honest comparison says when you should stay. Here are the cases where the community edition of Vibe Kanban is the right tool and AgentsRoom is not.
Vibe Kanban is released under the Apache 2.0 license: you can read the code, fork it and build it yourself, which matters more now that its community maintains it. AgentsRoom is not open source.
Vibe Kanban starts with npx vibe-kanban and opens in your browser. AgentsRoom is a desktop app for macOS, Windows and Linux, with iOS and Android apps; there is no browser version.
Vibe Kanban writes the pull request description with AI and takes you to the merge. AgentsRoom pushes the branch and opens your host's prefilled pull request page, and you finish it there.
If you never relied on the board and only started agents in workspaces, with a branch, a dev server and a preview each, those workspaces still run locally and you may have no reason to move.
Your repositories and your agent subscriptions stay where they are. Only the tickets need to move, and an agent can do it for you.
In Vibe Kanban, open a project and click Export data. You get a ZIP with your issues and projects as CSV files.
Download AgentsRoom for macOS, Windows or Linux and drag your project folders into it. Your CLAUDE.md and AGENTS.md files are detected automatically.
Give the CSV to an agent and ask it to create the tickets: through the AgentsRoom Backlog MCP, it writes them into your board. Already tracking work in GitHub Issues, Jira or Linear? Import from there instead.
See how AgentsRoom compares with the agent managers and terminals developers also look at.
Download and manage all your coding agents in 30 seconds. Free for 2 projects.
컴패니언 앱: 이동 중에도 에이전트를 모니터링
Claude, Codex, Antigravity CLI 또는 다른 AI 공급자를 사용하세요.
버그와 요청을 공개 백로그로 바로 보내세요.