Wanju vs. Vibe Kanban
(and its forks)

Vibe Kanban and its forks are good at what they set out to do: run several agent sessions in parallel against one repository and keep them organized on a board. If your problem is "I have one active project and want three agents working it at once," a board like that is a fine choice.

Wanju starts from a different problem: you have fifteen repositories and twelve of them are dead. The unit of work isn't a session — it's a project's distance from finished. Wanju scans your whole workspace or GitHub account, shows each repo's real stage, staleness, and single next step, and dispatches agents per project.

The second difference is the built-in gate. Edits from Wanju's built-in agent land as reviewable diffs and do not touch disk until you approve them; tests then run and the result is recorded.

Both are local tools. If you're deep in one project, use a board. If you're staring at a graveyard, scan it first and see what Wanju sees.