kanzo

English | 简体中文

Kanzo is a kanban board in your browser and an MCP server in one 4.7 MB program, so you and your coding agents work on the same tasks: on one computer, or on one board shared by all of them. No account, no server, no setup: run kanzo and it works.

You never edit a file. Everything is done in one of three places:

• the board, in your browser, for you;
• MCP, for your agents: they take tasks, move cards and comment;
• the kanzo command, for the terminal and scripts.

curl -LsSf https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.sh | sh

For macOS and Linux, including every Raspberry Pi. On Windows, in PowerShell:

powershell -ExecutionPolicy Bypass -c "irm https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.ps1 | iex"

Both add Kanzo to your PATH, for terminals you open from then on. To use it in the one you installed from, run source $HOME/.cargo/env (env.fish in fish), or open a new one.

Or download the Windows zip from the latest release and put kanzo.exe in a folder named bin on your PATH, like %USERPROFILE%\.cargo\bin: the board updates itself only there.

Every release is signed by GitHub: check a download with gh attestation verify <file> --repo emanuele-em/kanzo. Or with Cargo:

cargo install kanzo

kanzo

The board opens at http://localhost:4242. That's all the setup there is: the first run creates ~/kanzo, and the whole board lives in it.

• Select tasks: ⌘-click them, or drag on empty board space, then move, tag or delete them together. Drag one and the rest follow.
• List view: the list icon shows the same tasks as rows to sort and group.
• Human tasks: mark a task Human and agents leave it to you. The person icon shows only those.
• Images: paste or drop one into a task or a comment.
• Links: give a task a URL, like its pull request, and open it from its card. Agents set it with url.
• Files: [name](file:///path) in a description or comment opens in your editor.
• Task panel: drag its left edge to resize it, or expand it to the whole window. Double-click the edge to reset it.
• Sidebar: the panel button beside search folds it to its icons. Drag a project to reorder the list, for everyone on a shared board.
• App: in Chrome or Edge, Install app at the bottom of the sidebar makes the board an app of its own. ⌘1–⌘8 pick a project, ⌘9 the last one, ⌘0 all of them. On macOS, kanzo then opens it instead of a tab, on the default port.
• Updates: when a new version is out, the sidebar offers it. One click installs it.

claude mcp add kanzo --scope user -- kanzo mcp   # Claude Code
codex mcp add kanzo -- kanzo mcp                 # Codex

Other MCP clients: run kanzo mcp (apps like Raycast need the full path, from which kanzo), or use the running board at http://localhost:4242/mcp.

Then ask: "take the next task from kanzo and do it." The agent:

• finds the project from the git remote of its repo; link more repos from the project's ⋯ menu;
• moves the card to doing and comments as it works;
• on review, comments how to resume its session.

Turn on Backlog in Settings for a column agents leave alone, until you move its tasks to todo.

• Set it: type in Waits on, in a task's panel, to find tasks in its project and pick them. Agents pass waits_on.
• Until those tasks are done: next_task skips it, and its card is dimmed and says what it waits on. You can still move it yourself.
• What counts: only done. A task in review still blocks.
• Find them: filter by is:waiting.

The board's filter (f), search (/) and the filter of list_tasks and next_task all understand the same words, like on GitHub:

• Every part must match.
• - negates a qualifier: tag:billing -status:done.
• Qualifiers turn blue as you type them.

Anything else is plain text. Use quotes for a phrase, "on hold", or to look for text that reads like a qualifier, "tag:bug". Agents can't filter through a property you've hidden in Settings.

Two ways, neither with any setup: share one board live, or sync it between machines.

Several computers, one board, at the same time: everyone sees the same tasks, and every agent works on them.

1. On the computer with the board, click the share icon next to New task and turn on Share this board. Copy an address it shows.

2. On each other computer, click the share icon, paste the address and click Join.

Nothing restarts and nothing needs configuring. Their board shows the shared one, and their agents use it through the same kanzo mcp, still finding the project from the repo they work in. Turn sharing off, or click Leave, at any time.

From a terminal, or for an agent, it's kanzo share on and kanzo join <address>, then kanzo share off and kanzo leave.

The same two commands work wherever the board lives; only the address changes:

Your computer shares its board. Others join it from theirs, on the same network.

flowchart LR
  B["💻 Laptop B<br><code>kanzo#nbsp;join#nbsp;192.168.1.20</code>"] -- home network --> A["💻 Laptop A<br><i>192.168.1.20</i><br><code>kanzo#nbsp;share#nbsp;on</code>"]

A Raspberry Pi keeps the board. Every computer joins it, and none has to stay on.

flowchart LR
  A["💻 Laptop A<br><code>kanzo#nbsp;join#nbsp;192.168.1.50</code>"] -- home network --> pi["🍓 Raspberry Pi<br><i>192.168.1.50</i><br><code>kanzo#nbsp;share#nbsp;on</code>"]
  B["💻 Laptop B<br><code>kanzo#nbsp;join#nbsp;192.168.1.50</code>"] -- home network --> pi

The Raspberry Pi is somewhere else, over the internet. Put a VPN on the Pi and on each computer, like Tailscale, NetBird or WireGuard: kanzo share on then shows the Pi's VPN address too.

flowchart LR
  A["💻 Laptop A<br><code>kanzo#nbsp;join#nbsp;100.101.32.7</code>"] -- VPN --> net(("🌐 Internet"))
  B["💻 Laptop B<br><code>kanzo#nbsp;join#nbsp;100.101.32.7</code>"] -- VPN --> net
  net -- VPN --> pi["🍓 Raspberry Pi<br><i>100.101.32.7</i><br><code>kanzo#nbsp;share#nbsp;on</code>"]

On a Pi, kanzo service install keeps the board running after a restart. There are no logins: share only on a network you trust.

To carry the board between machines you use one at a time, a private git repo you own keeps it in step.

1. Create an empty private repo on GitHub, or anywhere git can push.
2. Click Settings at the bottom of the sidebar, choose Sync and paste its URL. Kanzo makes ~/kanzo a git repo and pushes the board.
3. On each other machine, do the same with the same URL: Kanzo offers to use the board that's already there.

From then on, choose Sync, or run kanzo sync, when you switch machines. It commits the board and pulls or pushes it, and it's safe while the board and your agents are running. If both machines changed the board, Kanzo asks which one to keep. To move to another repo, change it in Settings, under Sync.

Every command takes --home <dir> to use another data folder.

Everything lives in ~/kanzo: the board in kanzo.db, settings in config.toml. You never need to open either; use another folder with --home or KANZO_HOME.

port = 4242
listen = "127.0.0.1"   # sharing opens the board to your network; "0.0.0.0" keeps it open
mcp_http = true        # MCP at /mcp
editor = "/usr/local/bin/cursor"   # opens file:/// links; on macOS, your text editor without it

These settings stay on each machine: kanzo sync leaves them out.

Settings on the board:

• Task properties: turn one off, like tags or comments, to hide it there and leave it out of what agents get. Nothing is deleted.
• Language: English or Chinese, under Board.
• What's new: this version's notes, under About.

Measured on an Apple M4.

AGPL-3.0: use it, change it and share it; if you offer a changed version over a network, share its source too. To help, see CONTRIBUTING.

_{mcp-name: io.github.emanuele-em/kanzo}