docs/kanban/features.mdx
Every task card runs in its own git worktree — an isolated checkout of your repository. This is the foundation that enables parallel agent execution:
When creating a worktree, Kanban symlinks gitignored files (like node_modules) from your main repo rather than copying or reinstalling them. This avoids the overhead of running npm install for every task.
When enabled, agents automatically commit their changes to the worktree branch as they work. This creates a trail of incremental commits rather than one large diff at the end.
Auto-commit can be toggled in the Kanban settings.
When enabled alongside auto-commit, agents can automatically create pull requests when they finish their work. The agent generates a PR with the changes from its worktree branch.
Auto-PR can be toggled in the Kanban settings.
Task linking lets you create sequential workflows where completing one task triggers the next:
When combined with auto-commit, this creates fully autonomous pipelines — one agent finishes, its work is committed, and the next agent picks up where it left off.
Clicking a card opens a detail view with a full diff of all changes in that worktree. The diff viewer includes:
The sidebar chat gives you a conversational interface for managing the board. Instead of manually creating and configuring cards, you can ask the agent to:
The agent manipulates the board directly based on your instructions.
Kanban includes keyboard shortcuts for common actions:
| Shortcut | Action |
|---|---|
| C | Create a new task card |
| ⌘ + click | Link a card to another card |
Open the settings dialog to configure how Kanban behaves. Available settings include:
~ instead of full home directory paths for readabilityDefine frequently-used commands (like npm run dev or npm test) in the Kanban settings. These appear as play buttons on task cards, giving you quick access to run, test, or debug the application within a worktree without switching to a separate terminal.
Click the branch name in the navbar to open a full git interface. From here you can:
This lets you manage your repository without leaving Kanban or opening a separate git client.
Kanban works with CLI-based coding agents. It uses experimental features that bypass permissions and runtime hooks, giving agents more autonomy to work without interruption. Agents currently compatible with Kanban include:
and more. Check settings for all available agent runtimes
When you move a card to trash, the worktree is cleaned up but Kanban saves a resume ID. If you need to continue work on a trashed task, you can use this ID to pick up where you left off without starting from scratch.
For teams and organizations, Kanban access can be gated via Cline remote config. This allows administrators to control who can access the Kanban board within their organization, enabling phased rollouts or restricting access to specific teams.