git-kura is a conflict-aware keyed worktree coordinator for Git. It helps humans, AI coding agents, and reviewers run multiple task-specific worktrees in parallel while detecting and preventing conflicting edits early. Kura would makes it easier to delegate multiple tasks to AI agents without manually reasoning about every possible conflict up front. If a worktree is likely to conflict with another active task, Kura can stop it before changes are made.

Multi-agent development becomes fragile when several agents work against the same repository at the same time. Typical failure modes are: - an agent edits the wrong worktree because the path was selected manually; - a reviewer inspects a different checkout from the one used by the implementer; - two agents independently modify the same files and only discover the conflict at merge time; - a local hook, skill file, or tool setup drifts across worktrees and agents. Kura addresses these failure modes with two small primitives: - keyed worktrees: one stable key resolves to one deterministic branch and worktree; - path seals: a task claims the repository-relative paths it intends to edit, so other tasks can detect the overlap before editing, committing, or merging. Kura would makes it easier to delegate multiple tasks to AI agents without manually reasoning about every possible conflict up front. If a worktree is likely to conflict with another active task, Kura can stop it before changes are made.

Having a built-in visual conflict map or a simple web UI that shows which worktrees are touching overlapping files would be really helpful for keeping track of everything at a glance, especially when juggling more than three parallel AI agents. Right now it sounds like I'd have to rely on CLI output to understand the picture.

finally something that solves the multi-agent git mess i've been dealing with. ran two worktrees editing the same files and kura caught the conflict before i wasted a merge cycle.