Kraft
A local orchestrator for semi-autonomous software work. One FastAPI process plus a React SPA: work items enter as chains — ordered nodes materialized from a YAML template — and each node runs hook-point tasks through plugin adapters (a headless agent, a subprocess, a builtin). Every retry loop is capped; hitting a cap escalates to a person with the full trace. Gates stop the chain where a human decision belongs.
Runs on your machine, binds loopback by default, and edits your repos through git worktrees.

Start here
- Getting started — install, connect a repo, run a work item end to end, approve its gate.
- Concepts — chain, node, hook point, adapter, gate, cap: the whole vocabulary.
- Install —
uv tool install, Homebrew, or from source. - CLI reference — every
kraftverb, grouped by what it does. - Configuration — every field in
repos.yaml,registry.yaml,policy.yaml,access.yaml. - Agent integration — driving Kraft with
/kraft:*slash commands from a coding agent instead of the browser: onboarding a repo, checking its config, filing work, acting on gates. Install via the Claude Code plugin marketplace orkraft admin init. - Remote access — approving a gate from your phone.
- Inbound triggers — starting a chain from a cron schedule or a
webhook instead of typing into
kraft item create.
A gate stops the chain where a human decides
Approve, reject with a note that re-runs the producing node, or open the full detail view.

Search, ⌘K
Hybrid full-text + vector search across work items, pending actions, and linked documents.

Analytics
Lead time, cost, and where both go — by node, by repo, over whatever window you pick. Built from the same events the board renders live, not a separate pipeline.

Source
Kraft is on GitHub at itsOmidKarami/kraft, Apache-2.0 licensed. CONTRIBUTING.md covers getting a dev environment running and how releases work.