Moving from
Vibe Kanban.
Vibe Kanban has been community-maintained since Bloop shut down on April 10, 2026. The code is Apache 2.0 and it still works — nothing about the shutdown deleted it. This page is for people who've decided they want a board someone is paid to maintain. If that's not you, staying put is a legitimate choice, and we say why below.
Step 1 — translate the model Issues become stories
This is the only part of the move that requires any thought. Vibe Kanban is built around issues and workspaces; Instify is built around stories and projects. The shapes are close, but a story carries a goal and acceptance criteria shaped by your project's stack — so the agent gets a brief, not a title.
- Workspace → Project — points at the same local repo
- Issue → Story — plus a goal and acceptance criteria
- Run / attempt → Execution record — files touched, commands run
- CLI + browser → Native macOS app
Step 2 — set it up Your code never moves
Both tools drive coding agents against your local repository, so neither one owns your code. Point Instify at the same folder Vibe Kanban was working in and your branches and history are untouched. Set your stack and project goals once, and every run gets that context automatically instead of you re-explaining it.
- Download, open, and select your existing repo
- Set stack, goals, and conventions once per project
- Connect Claude Code or Codex — whichever you already use
Step 3 — the honest part There's no importer
We could pretend otherwise, but you re-create your board by hand. There is no automatic migration of cards, columns, or run history out of Vibe Kanban. In practice that's a few minutes: most boards have a handful of genuinely in-flight items, and the rest is backlog you'd rewrite as stories anyway.
- Re-create in-flight cards first — those are the ones that matter
- Old run history stays in Vibe Kanban; nothing is lost, it just doesn't come with you
- Backlog items are worth rewriting as stories rather than copying verbatim
Step 4 — what you gain Work that continues without you
The reason to move rather than just switch boards: when an agent hits its usage limit, Instify queues the story and auto-resumes it the moment the window reopens, instead of leaving the run dead until you notice. That's a Pro feature, and it's the one thing a board you have to watch can't do for you.
- Quota-interrupted work queues and resumes on its own
- Full execution history per story, not per session
- A company whose job is keeping it working as the agent CLIs change
Instify