Your agent says done. Loki proves it.
An autonomous software factory that knows what it is supposed to deliver, and proves it did.
git clone https://github.com/asklokesh/loki-mode
claude plugin marketplace add ./loki-mode/packages/loki-seal # then /plugin in Claude Code, install loki-seal
npx loki-mode tour # zero-key replay of a real Evidence Receiptloki-seal is a Claude Code Stop hook: when your agent tries to finish, it runs your repo's real test suite and refuses "done" if tests newly fail or if tests or CI config were deleted, skipped or weakened. Details: packages/loki-seal/README.md.
The Seal is the verdict loki-seal prints on every stop attempt: PASS with a receipt, or a block with the reason.
Hand it a PRD, GitHub issue, OpenAPI doc or one-line brief. It derives a delivery contract (the acceptance criteria), builds against it with a Reason, Act, Reflect, Verify loop, and ends with an Evidence Receipt that states what was proven and what was not. If the contract cannot be derived, it stops and asks one question instead of guessing.
npm install -g loki-mode # or: bun install -g loki-mode
loki quickstart # guided first build
loki start ./prd.md # build from a PRD
loki start owner/repo#123 # build from an issueWorks with Claude Code (full support), Cline, OpenAI Codex CLI, Aider and opencode.
Before a build counts as done, a review council selects reviewers from a specialist pool (agents/types.json, scored by run.sh:FOCUS_KEYWORDS). The bundled MCP server exposes 36 tools over stdio (mcp/server.py).
Opt-in: set LOKI_ENGINE=v10
Guide, provider table and summary format: docs/v10/GUIDE.md.
The previous long README moved, unchanged apart from link paths, to docs/README-FULL.md. It holds:
- Install methods (Bun, npm, Homebrew, Docker), the Claude Code plugin, and first-build commands
- Try it without installing, and read-only brownfield mode