Kander

English | 简体中文 | 日本語

Strict rule-driven multi-agent parallel development with built-in independent review and delivery gates to ensure automated delivery quality.

Born from real engineering
Since August 2026, Kander has driven nearly 1,000 production tasks in the QuickTUI production environment. Refined through handling actual code conflicts, race conditions, and complex bugs, it establishes truly reliable agent orchestration, independent review, and crash recovery. Even with lower-cost models, it guarantees delivery quality.

In-depth reading: Kander in Production | Full Production Retrospective (Deep Dive)

• Two-Stage Independent Review Gates: Physical isolation between execution and review. PMQA catches semantic and state-machine bugs, blocking false-green tests.
• Conflict-Aware Scheduling: Static analysis of Git branch overlaps and file modification boundaries ensures controlled concurrency without write conflicts.
• Terminal and Workspace Isolation: Isolated parallel agent execution powered by Git Worktrees and tmux/herdr containers.
• Zero-Token GitHub Integration: Seamlessly reuses local gh credentials to browse issues, import task cards, and sync progress directly from the board.

Running requires Git, plus at least one of Codex, Claude, Grok, Cursor, or Pi.

macOS — install with Homebrew:

brew install dualface/tap/kander

kander

Linux — download the binary directly:

ARCH=$(uname -m); [ "$ARCH" = x86_64 ] && ARCH=amd64; [ "$ARCH" = aarch64 ] && ARCH=arm64
curl -fsSL "https://github.com/dualface/kander/releases/latest/download/kander-linux-${ARCH}.tar.gz" | tar xz

./kander

Windows — download kander-windows-amd64.zip from Releases, unzip it, and run kander.exe.

On first launch, if not yet installed, an interactive wizard starts. Once installation finishes, it is ready to use.

Four steps to get going:

1. Start an agent session and discuss the requirement or task there, making the goal and acceptance criteria clear. The agent's Plan mode is recommended.
2. Once the task is confirmed, the agent (with Kander rules loaded) confirms whether to launch it through the kanban flow. Confirm, and the task is created and started automatically.
3. When you have multiple requirements, repeat steps 1-2 for each one, continuously scheduling and launching tasks.
4. Check task status with the command-line interface:

kander

The board contents above come from my real project https://quicktui.ai. QuickTUI is a tool for remotely operating the agents on your computer; it supports iOS/Android/macOS/Linux/Windows and is free to use.

Further reading: the slides How to Advance Tasks Efficiently (PDF).

• kander: Open the interactive terminal kanban board.
• kander doctor: Check and repair environment dependencies, agent availability, launchers, and rules configuration.

Linking a project to a GitHub repository needs the GitHub CLI (gh). Kander never asks for, reads, or stores a token; it reuses the credentials gh already manages.

On the terminal board, press g to open the GitHub issue list in an overlay.

A: Stop the agent currently working on the card, launch a new agent, and prompt it to take over and continue task card TASK-ID (replace TASK-ID with the actual card ID). In the terminal kanban board, select the card and press y to copy its task ID.

A: Copy the task card ID, launch an agent, and instruct it to act as the coordinator to take over and advance the task group containing TASK-ID.

A: Start an agent (with Kander rules loaded) and directly ask for the current status and progress of any unfinished task cards.

• Review Disposition & Completion Gate
• Card Transactions & Crash Recovery
• Terminal Backends & Container Definitions
• Durable Dispatch Protocol
• GitHub Issue Import & Result Protocol

This project is under the MIT License; see LICENSE.

Release notes live in CHANGELOG.md.