Vibe Kanban separates planning issues from agent workspaces. Aiola offers project task boards, chat threads, terminals, and scheduled prompts in one desktop app. Here is how those workflows compare after the company behind Vibe Kanban closed.
What does Vibe Kanban do?
Vibe Kanban's docs describe kanban issues for planning and workspaces where coding agents run. The docs say the product is not a coding agent. Named options there include Claude Code, Codex, Gemini CLI, and OpenCode. The getting started guide says to run npx vibe-kanban and open the UI in a browser. Its agent list does not name Grok CLI or Antigravity.
Creating a workspace builds git worktrees for the repositories you choose and starts the agent. One issue can link to several workspaces, so those agents can run in parallel. Finished work can become a GitHub pull request or a local branch merge. The workspaces overview adds an integrated terminal, a preview browser, and a changes panel.
On April 10, 2026, bloop said it was closing the company behind Vibe Kanban. That shutdown notice says the project stays open source and community maintained. Remote services were set to remain for 30 days, then the app would become fully local. The notice names kanban issues, comments, projects, and organizations among the services scheduled for removal. Local workspaces were set to keep working, and paid subscriptions were terminated.
Why look at a desktop app?
You may want one desktop app on macOS 12+ or Windows 10+. Aiola has no Linux build, so a Linux machine stays on another tool. Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity can run in this app. Each CLI uses the subscription you already pay for, with no token markup.
The task docs describe CSV imports with Append and Replace modes. Append adds records, while Replace replaces the current board. They do not describe a Vibe Kanban history migration.
Vibe Kanban's command bar docs list Ctrl+K on Windows and Linux, and Cmd+K on Mac. Both products document Windows usage, so Windows support alone does not distinguish them.
Aiola is a free download. Pro costs $24 a month or $240 a year. GUI Lifetime is a one-time purchase at $49, $89 or $129.
How does the task board start an agent?
Open Tasks inside the workspace that owns the repository. In Aiola, a workspace means one project, not the whole product. The board and the list show the same records for that project. Workspace and Central pages remember their own board or list choice. Central Tasks brings project-aware records into one view across projects.
Nine statuses run from Backlog and Todo through Scheduled, In Progress, and Blocked. Human Review, Create PR, Complete, and Cancelled finish that list. Send a task to In Progress and its configured agent workflow starts. Create PR is the status that starts pull-request creation. Auto-create-PR can send a successful run to Create PR instead of Human Review.
Local mode runs in the workspace checkout, and Worktree mode uses an isolated Git worktree. Project Settings, then Tasks, sets the default run mode and auto-create-PR. You can still override the run mode on one task.
Fields include priority, labels, a scheduled date and time, comments, subtasks, linked tasks, and file or image attachments. Mentions cover files, tasks, agents, App Logs, Feedback, workspaces, issues, and pull requests. The task chat retains the task context while the timeline records status changes.
Where do threads and terminals sit?
A draft becomes a thread when you send its first message. That thread keeps its original workspace, and you cannot move it to another project. Available composer controls depend on the provider. Choices can include the agent, model, reasoning, Fast Mode, and permission mode. Context choices can lock after the thread starts.
The dashboard strip can show Review, browser tabs, Files, and a terminal. Tabs can be reordered or closed, and the panel can expand beside chat. An existing thread can also open in its own desktop window.
What can you schedule beside the board?
An automation is a saved prompt with a fixed workspace and run setup. Schedules can be Daily, Weekdays, Weekly, Interval, Manual, or a custom RRULE. Each job is Active, Paused, or Disabled, and it uses its configured timezone. You choose the provider, model, agent, and reasoning level for that prompt. Create one from scratch, or start from a preset in the in-app catalog.
Run a manual automation from its detail page. Manual automations have no automatic run. The detail page reports the next run, last result, errors, and linked threads. These jobs run while the desktop app is open. You edit them in the workspace, since there is no Central editor. Central Home and Central Calendar show that activity across projects.
Which other tools should you check?
Conductor and Crystal have different availability and maintenance status. Their current documentation gives these starting points.
| If this is your case | Where to look |
|---|---|
| You want a Mac app for Claude Code, Codex, or Cursor | Conductor install guide |
| You want the local open-source project | Shutdown notice |
| You still run Crystal | Crystal repository |
Conductor's install guide says the app is for macOS, not Windows or Linux yet. It requires GitHub authentication and at least one agent provider. Setup checks cover Claude Code login, Codex login, or a Cursor API key. Crystal's repository says the app was deprecated in February 2026 and replaced by Nimbalyst. Its repository directs users to Nimbalyst for downloads, documentation, and updates.
Try it in Aiola
Download Aiola free for macOS 12 or later and Windows 10 or later. Add your repository, open Tasks, and choose Local or Worktree mode for a task.
