⌥ One worktree per ticket
Every ticket runs in its own isolated git worktree. Agents work side by side without ever touching each other's files.
// terminal kanban · ai agent orchestrator
A terminal Kanban board that orchestrates AI coding agents — Claude Code, Codex, and Copilot — as zellij sessions. Each ticket gets its own isolated git worktree, so agents never step on each other.
┌─ features
Every ticket runs in its own isolated git worktree. Agents work side by side without ever touching each other's files.
Moving a ticket to In Progress launches the agent in a dedicated zellij session and drops you in. Detach with Ctrl+o d — it keeps running.
Claude Code, Codex, and Copilot out of the box via configurable command templates. Point it at any CLI you like.
Give a ticket an initial prompt and the agent starts working the moment its session opens. Create tickets from the CLI, too.
A single global database keeps your board intact across projects, restarts, and reboots. No services to run.
Catppuccin, Tokyo Night, Gruvbox, Nord, or your terminal's own 16 colors — switch live in-app with t.
Kamaji checks for new releases on launch. When one's available the status bar prompts you — press u to download and replace the binary in place, then restart.
┌─ how it works
Press c. Add a title, optional description, an initial prompt, and pick the agent.
A git worktree is created, a zellij layout is generated, and the agent launches with your prompt — auto-attached.
Re-attach any time with ↵. When it's ready for eyes, move it to Review.
Move to Done and Kamaji offers to kill the session, remove the worktree, and delete the branch.
┌─ quick start
$PATH$PATH; project roots must be git reposclaude, codex, copilot$ curl -fsSL https://raw.githubusercontent.com/alveflo/kamaji/main/install.sh | sh $ kamaji # installs a prebuilt binary to ~/.local/bin (override with KAMAJI_INSTALL_DIR) # or build from source: $ cargo build --release && ./target/release/kamaji # seed a ticket without opening the TUI: $ kamaji ticket create --prompt "Fix GitHub issue #123"