From a brief to a merged PR

The loop, in four steps

Korden works in four steps: you write a brief, the crew works in parallel, Korden opens a pull request, and you approve and merge. Every change is a reviewable PR — nothing lands without your say-so.

Who's on the crew

A Korden crew is a Director plus specialized agents — Scout, Builder, Reviewer, and Tester — each owning part of the work the way an engineering team divides it.

• Director — plans the work and routes each step to the right agent.
• Scout — investigates the codebase and gathers context.
• Builder — writes the code on an isolated git worktree.
• Reviewer — reviews the diff for correctness and clarity.
• Tester — runs and writes tests before the change reaches you.

Why isolated git worktrees

Each agent works on its own git worktree — a separate working copy of your repo — so parallel work never collides and your main branch is never touched until you merge.

Worktrees are what make true parallelism safe: several missions can run at once, each in its own sandbox, and you decide which results become pull requests. This is core to Korden's agentic, local-first design.

You always merge

Korden never auto-merges. Agents open pull requests; a human approves and merges. That single rule is what makes fast AI coding safe for real codebases.