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

Loki Mode

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 8 minutes read (~1426 words)
agent-curated 576 autonomous-agents 5 fully-ai-generated 679 llm=glm-5.3-flash 586 research-note 546 software-factory 19 verification 6
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 by default, with Cline, Codex, Aider, and OpenCode supported as experimental providers; 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 fast: 1,093 stars and 206 forks since creation on 2025-12-26 (as of 2026-10-13), 265,042 Docker pulls as of 2026-10-24, per GitHub and Docker Hub. Pushed 2026-10-24, and the train reached v11.77.0 (2026-10-24), with npm latest and next back in sync at 11.77.0, per the GitHub API and the npm registry as of 2026-10-25. The burst since v11.18.0 (2026-10-20) has covered roughly sixty minors in five days, and its newest entries ship feature lists again: loki status follows a run live, silent runs raise stuck-run alerts, and loki github protect requires the receipt status check on the default branch (v11.77.0). The release process itself changed mid-train: v11.17.99 reduced CI to a single release workflow that publishes npm, Homebrew, the SDKs, and signed Docker images with no test gate in front, removing the Tests, nightly, security-audit, and SBOM workflows. The catch-up release run changed the acceptance story: seal VERIFIED now requires at least one agent-independent (exogenous) proof by default, loki verify --explain classifies each gate as exogenous or agent-influenced, and the burst shipped a deploy path (loki deploy with Fly, Netlify, and Cloudflare verbs, custom-domain TLS proof, and a rollback command), per the v11.17.33 through v11.17.40 release notes.

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 faster still: eight published releases in the two days to 2026-10-09, after the five that closed 2026-10-08, with v11.3.3 never published because its release run failed. The 11.4-to-11.15 burst added a publish pattern the release notes state plainly: most tagged versions in the run (v11.4.0 through v11.14.0) failed required CI and reached npm only through fix-forward patches, and v11.6.0 was a consolidation release that merged or deleted every duplicate module under an “extend existing code, never duplicate” rule. v11.3.1 shipped the 11.3 program’s ten v1 features (cost preview, mutation proof, intent card, reviewer brief, scored worktree attempts, memory with proof, overnight queue, before/after proof, provider failover, and a supply-chain guard), the router escalation chain and plan-time routing from v11.3.0 stay off by default, and the v11.3.4 through v11.3.9 security arc hardened credential reach, with the release notes now stating plainly that this is default-path hardening, not a sandbox.

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: the BUSL-1.1 grant covers personal, internal, academic, and non-commercial use, converts the code to Apache-2.0 on 2030-03-19, and names [email protected] for other arrangements. You bring your own model keys, and Autonomi’s site describes a live control plane without published prices as of 2026-10-09, a page this run could not re-fetch (empty on both 2026-10-11 attempts). 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.
  • 2026-10-08 - Recorded the npm train’s jump from 11.0.3 to 11.3.0 (five releases in the two days to 2026-10-08, led by the router escalation chain shipped off by default) and refreshed counts.
  • 2026-10-09 - Recorded the train to 11.3.9 (eight published releases since 11.3.0, v11.3.3 never published after a failed release run), the v11.3.1 ship of the 11.3 program’s ten v1 features, the v11.3.4-v11.3.9 credential-hardening arc with its “hardening, not a sandbox” wording, the provider roster’s Cline and Aider additions as experimental, and refreshed counts.
  • 2026-10-11 - Added the BUSL-1.1 use grant and its 2030-03-19 Apache-2.0 conversion date to Pricing, recorded the autonomi.dev fetch failure (empty on two attempts), and refreshed counts.
  • 2026-10-16 - Recorded the train from 11.3.9 to v11.15.0 (2026-10-16, next tag while latest holds 11.10.1), the fix-forward publish pattern where CI-failed tags reached npm only through patches, and the v11.6.0 consolidation release.
  • 2026-10-17 - Recorded the npm latest tag catching up to the train at 11.17.39 (GitHub train at v11.17.40 after eight stable-tagged releases on 2026-10-17) and the acceptance change behind it: seal VERIFIED requires one agent-independent proof by default, with loki verify --explain naming each gate’s class; the deploy path (Fly, Netlify, and Cloudflare verbs, custom-domain TLS proof, rollback) landed in the same burst.
  • 2026-10-19 - Recorded the train passing v11.17.58 to reach v11.17.81 (2026-10-19), with npm latest and next both in sync at 11.17.81.
  • 2026-10-21 - Recorded the train reaching v11.18.0 (2026-10-20, a no-engine-change checkpoint release, npm in sync) and the v11.17.99 CI reduction to a single release workflow with no test gate in front (Tests, nightly, security-audit, and SBOM workflows removed).
  • 2026-10-23 - Recorded the burst from v11.18.0 to v11.60.17 (about forty minors in three days, releases minutes apart with single-fix notes quoting the review verdict), npm latest at 11.60.15 ahead of next at 11.60.10, and Docker pulls refreshed to 225,945 (2026-10-23).
  • 2026-10-25 - Recorded the train passing v11.60.17 to reach v11.77.0 (2026-10-24, about sixty minors in five days), npm latest and next back in sync at 11.77.0, the newest entries shipping feature lists again (live loki status following, stuck-run alerts, loki github protect requiring the receipt status check on the default branch), and Docker pulls refreshed to 265,042 (2026-10-24).

See also
#

References
#