| Completely different philosophies. I will share a TL/DR below: MY KANBAN CLI IS: A project management system to plan, estimate, track sprints, measure velocity, assign roles, and give agents structured tasks with acceptance criteria. CLINE KANBAN IS: An agent execution platform to run multiple AI agents in parallel on isolated worktrees, review diffs in a web UI, and auto-commit/PR their output. SIMILARITIES: - Local - Git integration with worktree support - Agent integration with parallel execution - Task and dependency tracking DIFFERENCES: - Language: Rust 2021 vs TypeScript/Node.js - Interface: Terminal CLI (JSON output) vs Browser web app (React SPA) - Task Creation: Human-focused vs Agent-focused - Agent Control: Agent runs the tool as a CLI utility vs Platform spawns and manages the agent as a child process - Core Engine: Sprints, story points, velocity, and role-personas vs MCP server management, web diff viewers, and auto-PR toggles - Lifecycle: 8-state validation engine vs 4-column drag-and-drop layout - Concurrency: File locking (fd-lock) for safe multi-agent CLI access vs Git worktree isolation for massive parallelism (hundreds of agents) - Output Target: JSON by default (agents consume it) vs Web UI by default (humans consume it) - Self-Management: Recalibration engine (auto-heal data, reorder tasks, rebalance sprints, archive) vs Not present - People Registry: Humans tracked separately from agents (people.json) vs Not present - Storage: JSON files in .kanban/ (atomic writes, two-tier locking) vs Runtime state streams + config files (no persistent task database) - Statistics: Cycle time, lead time, revisions, blocks, effort ratio vs None - Coordination: Shared with teammates via git vs Independent instance There are many more differences between the two, which brings me to my first point. All in all, I see my Kanban as being a much more structured, human-centric, and controlled environment, since it's a complete management system rather than just an execution layer. You can practically plan the whole project using my tool, before any implementation even starts. That means complete project structure (via files_to_modify), acceptance criterias (+ context), commit messages, branch names, version bump (handled automatically by the tool as tasks are completed) and so on. It's a full project trace, which uses the full potential of a human + agent development workflow. |