What is Kanzo?
Kanzo is a kanban board that runs in a browser and an MCP server that lets coding agents work with the same tasks. It is designed for developers who want to coordinate their own work with agents on one computer or across a shared board. The board is stored on your computer, and you can start it from the command line without an account or a separate server.
Kanzo Features:
Browser Kanban: Create tasks, move cards between status columns, add descriptions and tags, and open task details in a resizable panel.
Agent Controls: Connect MCP clients so agents can find tasks, move cards, add comments, and identify projects from repository Git remotes.
Task Dependencies: Set tasks to wait on other tasks; agents skip blocked work until its dependencies are marked done.
Search and Filters: Search across projects and filter by status, tags, dates, task fields, comments, images, or whether a task is waiting.
Board Views: Switch between a kanban board and a list view, group or sort tasks in the list, and select multiple cards to edit together.
Shared Board: Let computers join one live board, or sync the board between machines using a private Git repository you own.
Kanzo Benefits:
Shared Context: You and your agents can work from the same task list, making task status and agent progress visible in one place.
Fewer Collisions: Dependencies help prevent agents from starting tasks before prerequisite work is finished, while human-marked tasks stay for you.
Faster Retrieval: Search and detailed filters make it easier to find relevant work across projects without scanning every card.
Flexible Workflows: Board and list views, backlog tasks, and grouped filters let you organize work in ways that suit different project needs.
Local Operation: Keeping the board on your computer avoids setting up an account or a separate server to get started.
Use Cases:
Agent Task Handoff: Give a coding agent a task to take, track its progress through the board, and review its comments when it finishes.
Pull Request Tracking: Attach a pull request URL to a task so you can open the related work directly from its card.
Dependency Planning: Map work that must happen in sequence, such as holding implementation until prerequisite tasks are complete.
Personal Backlog: Park ideas in a backlog column for later, then move selected tasks into the active workflow when ready.
Multi-Computer Work: Keep a team or personal board available across computers by sharing it live or syncing it through a private Git repository.

