Loki Mode

Loki Mode, built by Autonomi, is a CLI-based autonomous software factory that takes a GitHub issue or a one-line task and returns a pull request accompanied by a signed receipt. The receipt lists the checks that ran and what was NOT PROVEN. It runs on the user's machine with their own model provider, such as a Claude Code login or an API key.

What It Is

Loki Mode is a source-available issue-to-PR engine. The current Loki 10 engine moves a task through intake, plan, wall, implement, verify and seal, then opens a pull request. Each run ends in one named outcome: VERIFIED, ALREADY_SATISFIED, FAILED, BUDGET_STOP, BLOCKED or STALLED. A run that cannot be verified opens a draft PR. It accepts GitHub, GitLab or Jira issues, or plain-text tasks.

Signed Receipts and Verification

Every run writes a receipt signed with a local Ed25519 key. loki verify re-hashes the receipt, checks its signature and compares it against the run's event log, returning VERIFIED, TAMPERED, UNCHECKED or UNSIGNED with distinct exit codes suited to a CI gate. The public key can be exported for verification on another machine. The docs state that a receipt claims only what its checks ran; signing proves who produced it, not that the code is bug-free. A companion Claude Code Stop hook, loki-seal, refuses "done" when tests newly fail or were weakened.

Control Plane and Workflow

A local browser UI, the Control Plane, is on by default and listens on 127.0.0.1. It lets users start, stop, retry and resume runs, edit loki.yaml, check receipts, watch cost and answer BLOCKED runs. loki backlog runs a queue of issues in parallel. Docker and Helm deployment are documented, and the bundled MCP server exposes tools over stdio.

Setup Path

Install with npm install -g loki-mode (Bun, Homebrew and Docker are also offered), run loki doctor to check prerequisites, then loki owner/repo#123. Claude Code is the primary provider; Codex, Cline, Aider and opencode are experimental. The license is BUSL-1.1, which is not an OSI open-source license, and converts to Apache 2.0 on March 19, 2030.