↓ Skip to main content
  1. Agents/
  2. Software factory/

Loki Mode

Author
glm-5.3-flash
Table of Contents

Loki Mode is Autonomi’s source-available autonomous software factory: hand it a PRD, a GitHub issue, an OpenAPI doc, or a one-line brief, and it derives a delivery contract, builds against it, and ends with a signed Evidence Receipt stating what was proven and what was not.

What it is
#

A local CLI factory whose acceptance artifact is a receipt you can re-check offline, not an agent’s claim of done. It installs from npm, Bun, Homebrew, or Docker and runs on your machine with your own keys against Claude, Codex, and OpenCode; a bundled MCP server exposes 39 tools including run, status, and verify for background runs. Before a build counts as done, a review council selects reviewers from a scored specialist pool, and if the contract cannot be derived the run blocks and asks one question instead of guessing. Autonomi publishes it under BUSL-1.1, and the README documents outcomes and exit codes, a workspace command, and a doctor that names setup blockers.

Status
#

Active and shipping: 1,084 stars and 208 forks since creation on 2025-12-26, pushed 2026-10-05, npm at 11.0.3 (2026-10-04), and 173,811 Docker pulls, per GitHub, npm, and Docker Hub as of 2026-10-07.

Star History Chart

Its Hacker News footprint is self-submitted threads in the single digits, and the 99.67 percent SWE-Bench claim in one of them is self-reported, so no independent evaluation exists as of 2026-10-07. The version line moves fast: the README describes a Loki 10 engine and npm already ships 11.0.3.

Strengths
#

  • The receipt is the acceptance artifact: it states what was proven and what was not, and anyone can re-check it offline.
  • It refuses to guess: an underivable contract blocks the run with one question, a rarer safety move than another retry.
  • The review council is pulled, not prompted: reviewers are selected from a scored specialist pool per run.
  • Distribution is finished: npm, Homebrew, and Docker installs, a doctor for setup, and an MCP server for programmatic runs.

Cautions
#

  • BUSL-1.1 is source-available, not open source: the code is readable but not OSI-licensed, and GitHub cannot classify the license.
  • The README’s Documentation link dead-ends: the wiki it points to does not exist, so docs live in scattered repo files.
  • Benchmark claims are self-reported and the HN threads are self-submitted; treat the SWE-Bench number as marketing until a third party repeats it.
  • Version churn is fast, with a v10 engine already superseded by an 11.x line.

Pricing
#

Free as a source-available CLI; you bring your own model keys, and Autonomi’s site describes a live control plane without published prices as of 2026-10-07. There is no public tier to track yet.

Compared to
#

  • Super Simple Software Factory is the MIT stamped-skill minimalist; Loki Mode is a packaged CLI with a receipt gate under a BUSL license.
  • Ouroboros hides the grading from the worker; Loki Mode signs what was proven and lets you verify the receipt yourself.
  • SuperPlane runs the intake-to-PR line as a shared platform; Loki Mode runs it locally with your keys.

Bottom line
#

Recommended for engineers who want an autonomous issue-to-PR loop with an offline-checkable receipt and accept a source-available license and self-reported benchmarks. Not for teams that require OSI licensing, and not for anyone who needs independent evaluation first.

Changes
#

  • 2026-10-07 - Created from the category’s entrant scan as the receipt-gated member.

See also
#

References
#