If you landed here, you've probably noticed the same thing we did: Vibe Kanban is winding down. The project's momentum has stalled and its website no longer resolves, which leaves a lot of builders looking for somewhere to take their workflow. The good news is that the idea Vibe Kanban championed — a Kanban board that orchestrates real coding agents — is very much alive. The better news is that you can now have it with a portfolio layer, agent choice, and an autonomous build loop on top.
This guide covers what made Vibe Kanban worth using, what to look for in a replacement, and an honest walkthrough of where Command Fleet fits.
What Vibe Kanban got right
Vibe Kanban popularized a simple, powerful framing: stop thinking of an AI agent as a chat window and start thinking of it as a worker you assign cards to. A few things made it click:
- Board-driven work. Tasks moved across columns, so you could see what an agent was doing at a glance.
- Multiple agents. It wasn't locked to a single vendor — you could point it at different coding agents.
- Local execution. It ran on your machine and worked against your real git repositories.
That combination — board + multiple agents + local — is exactly the right foundation. The question is what to build on top of it.
Migrating now? Your projects are just git repositories on disk. Nothing about Vibe Kanban locked your code in, so moving to another local tool is mostly a matter of pointing the new app at the same folders.
What to look for in a Vibe Kanban alternative
If you're choosing a replacement you'll live in every day, weigh it against five things:
- Is it maintained? The whole reason you're here. Pick something with an active roadmap.
- Does it scale past one repo? Most tools assume a single project. If you ship a portfolio, you want workspaces and projects, not a hundred browser tabs.
- Is it agent-agnostic? Claude Code, Codex, and Gemini are each better at different things. Lock-in costs you flexibility.
- Is it safe to run unattended? Isolated git worktrees, an in-app diff, and a review-before-merge step are non-negotiable once agents start editing real code.
- Does it stay local? If your code or your clients' code can't leave your machine, a cloud agent is a non-starter.
Where Command Fleet fits
Command Fleet keeps everything that made the Kanban-over-agents model great and extends it for people who run more than one thing.
It's built for a portfolio, not a repo
Command Fleet organizes work as organizations → workspaces → projects → tasks. Each project gets its own board, and a home dashboard rolls up what's running, what's waiting on review, and a live activity feed across everything. If you're a solo founder with seven apps or an agency with a workspace per client, this is the layer you were missing.
It's genuinely agent-agnostic
Dispatch any task to Claude Code, Codex, or Gemini — chosen per task and switchable anytime, with an optional per-run model override. Use a cheaper model for boilerplate and the strongest one for the gnarly refactor, all from the same board.
It's safe by default
Every run happens in its own git worktree on a dedicated branch. Parallel agents never clobber each other or your working tree. When a run finishes you get an in-app diff with +/- coloring and a one-click merge — or you discard it. An optional verify gate can run your build and tests and bounce a "done" task back to review if it fails.
It can build the whole thing
This is the part Vibe Kanban never had. Describe an app to the workspace manager and it scaffolds the project from a stack pack, breaks the work into an ordered task graph, dispatches each task to an agent, auto-retries failures, merges finished branches, and can deploy — across six stack packs from Firebase to Fly. You stay the reviewer; it does the typing.
It stays on your machine
Projects, data, and API keys never leave your computer. Keys live in your OS credential vault, and a per-project secrets vault is never sent to any agent. You bring your own Claude, Codex, or Gemini subscription, so you're never double-charged for model usage.
Side by side
| Capability | Command Fleet | Vibe Kanban |
|---|---|---|
| Kanban over real agents | Yes | Yes |
| Multiple agents | Claude · Codex · Gemini | Multi |
| Local-first | Yes | Yes |
| Many projects / portfolio | Yes | Single-repo |
| Autonomous plan → build → deploy | Yes | No |
| Built-in preview & deploy | 6 stack packs | No |
| Maintained & available | Active | Winding down |
How to migrate in three steps
- Install Command Fleet and create a workspace (one per client or product line works well).
- Add your existing projects by pointing Command Fleet at the same git folders you used before. Set a setup script (like
pnpm install) so fresh worktrees build. - Recreate your active cards as tasks, pick an agent, and dispatch. Review the diff, merge, and you're back in motion — now with a board per project instead of one big list.
If Vibe Kanban taught the industry that agents are workers you assign cards to, Command Fleet is what that idea looks like once you're running a whole fleet.
Pick up where Vibe Kanban left off
Portfolio-scale, agent-agnostic, autonomous, and 100% local. Free for 14 days, no credit card.