Kraft Lite
Kraft Lite runs a chain of work inside a single agent session: the same ordered nodes, human gates, and fix-loop caps as Kraft, with no service, port, or database process. It is the attended half of Kraft. The chain runs in front of you and resumes across sessions, but it doesn't outlive your terminal.
Unlike the kraft plugin, Lite needs neither
the kraft binary nor an MCP server. It needs Python 3.10 or newer and nothing
else.
Install
Lite ships in the same plugin marketplace as the kraft plugin:
claude plugin marketplace add itsOmidKarami/kraft
claude plugin install kraft-lite@kraft
Add --scope project to either command to keep it to one repo. Update with
claude plugin update kraft-lite.
To check the install, run /kraft-lite:init in a repo, then
/kraft-lite:status. Status reports that no chain is running yet.
Slash commands
| Command | What it does |
|---|---|
/kraft-lite:init | Once per repo: detects the test command and which installed skills can run each node, and writes an editable .kraft-lite/registry.yaml. |
/kraft-lite:start | Materializes a chain's nodes and runs the first one. |
/kraft-lite:next | Runs the next node, or resumes one after a gate, a new session, or a cleared context. |
/kraft-lite:gate | Presents what a blocked gate needs decided, then records the approval or rejection. |
/kraft-lite:status | Reports which node is live, what blocks it, and how many fix attempts are spent. |
Behavior
- Nodes. The packaged chain runs from spec through plan, implementation, verification, and review, with gates where a human decides.
- Who runs each node. Lite supplies the order, the gates, and the caps. The registry binds each node to a skill you already have, and Lite calls it. Lite doesn't supply a spec writer or a planner.
- Freezing. A chain freezes when it starts. You can't reorder, add, or remove its nodes. The registry is reread on every dispatch, so rebinding a node in it corrects a chain already in flight.
- State. Lite keeps state in beads (
bd) when the repo has it, and otherwise in.kraft-lite/chain.jsonl. The format is the samebd exportformat either way, so adoptingbdlater isbd import. - Several chains. One directory can hold several chains. With two or more
unfinished chains, each command needs
--chain-id <id>.
What Lite doesn't do
Lite has no unattended execution, web board, unattended CI waiting, spend caps, or cross-repo search. For those, use Kraft.
More detail
The Kraft Lite README is the source of truth for the chain's contents, what runs each node, and state handling. It changes faster than this page.