Switch from Vibe Kanban to Task Machine

Vibe Kanban is an open-source kanban board for AI coding agents: you plan issues and sub-issues, assign tasks to agents, run several in parallel across git worktrees, review diffs in a built-in viewer, and track status against pull-request activity. Since Bloop shut down in April 2026, the community maintains it. Task Machine runs recurring work of every kind, with code as one part of it, and brings every decision to one Inbox.

Why do people switch from Vibe Kanban?

• Work beyond code has nowhere to go. Outreach, client reports, content, and support do not fit a board built around worktrees and pull requests. Task Machine tasks carry any kind of work, and the catalog of 140 playbooks across 17 categories covers operations well beyond engineering.
• Review beyond the diff. A diff viewer reviews code. Task Machine's approval and question steps cover any consequential output, such as a draft email, a report, or a plan, from one Inbox, and verifier checks test work before it reaches you.
• Recurring work instead of one-time cards. A card runs once. Task Machine runs explicit workflows on schedules, with the same steps in the same order and a run history every time.
• A maintained, hosted product. With the company behind Vibe Kanban gone, its roadmap depends on volunteers. Task Machine is a hosted product with ongoing support.

What maps to what?

Prices and features were checked against each vendor's own pages on 6 October 2026.

What do you give up?

Vibe Kanban is more focused for parallel coding agents and code review, and it is free and open source under Apache 2.0, so you can run it yourself. If your whole job is shipping code through many agents in parallel, it fits that job closely. The work worth moving is the recurring business work around the code.

How does the switch work?

1. Separate the work. Parallel coding can stay on the board, and recurring business work and anything that needs a structured approval are the candidates.
2. Create your Task Machine workspace, connect the accounts that work touches, and pick playbooks that match the jobs.
3. Rebuild each candidate as a workflow, with agent steps for the work, an approval step where you want the final say, and a verifier check where quality has to be tested.
4. Run a cycle, compare the result with how you handled it before using the run history, then retire the manual version.

Common questions

Can Task Machine run coding work too?

Yes. Agents run coding tasks in the Cloud or on a computer you connect, where tamacode can use your own ChatGPT, Claude, or GitHub Copilot subscription. Task Machine is organized around workflows and decisions more than worktrees.

Can I use both?

Yes. Vibe Kanban can handle parallel coding work while Task Machine runs the recurring operations around it.

Do agents act without my approval?

Only where you allow it. Each agent has an autonomy level, the default sends consequential actions to your Inbox, and budgets warn you as spending nears the limit.