OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Coding Agents

Loki Mode

Loki Mode is a local command-line coding agent that turns software tasks, specifications and tracker issues into code changes and pull requests, with signed receipts that can be checked offline.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Loki Mode — OpenViST project profile in Coding Agents.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Loki Mode when a software task can be stated clearly enough for an agent to derive checks, implement the change and return work for review. It is also relevant when reviewers need a signed record of the run and its checks.

Who it is for

  • Developers who want to delegate a defined code change and review the resulting pull request.
  • Teams that need a receipt recording a run’s outcome and checks.
  • Maintainers coordinating a change across multiple repositories.

Documented uses

  • Submit a short task, PRD file or GitHub, GitLab or Jira issue for implementation.
  • Generate and review a pull request that summarizes the requested work, changes and checks.
  • Verify a run receipt locally or export a public key for verification on another machine.
  • Combine child receipts for a multi-repository change set.
Before you choose

Requirements & limits

Loki Mode is distributed as a CLI with npm, Bun, Homebrew and Docker installation options. The README documents macOS and Linux support. Its primary workflow requires a model provider; Claude Code is the default, with an Anthropic API-key option for the main start path.

  • The documented baseline requires Python 3.8+, Node.js 18+ (20+ recommended), jq, Git 2.x and curl.
  • Claude Code is the default provider and is documented as the only provider with every feature; loki edit and loki chat call the Claude CLI.
  • Loki may stop and ask a question if it cannot satisfy the task contract as written.
  • A run that does not verify opens a draft pull request; receipts report their checks but do not prove code is bug-free.
  • The project documents a tour command that prints a receipt from a past build without a key, spend or network access.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up Loki Mode and start a coding task

Install the CLI, prepare its documented requirements and submit a task for implementation and pull-request handling.

Before you start

  • macOS or Linux
  • Python 3.8 or later, Node.js 18 or later, jq, Git 2.x and curl
  • Claude Code installed and logged in, or an Anthropic API key for the main start path

Steps

  1. Install Loki Mode with the command below.

    Documented command
    npm install -g loki-mode

  2. In the target repository, run loki setup to use the first-run wizard.

  3. Submit a task with loki start "add rate limiting to /api/login", a PRD file such as loki start prd.md, or a tracker issue reference.

  4. Review the resulting pull request and its stated checks and outcome.

Expected outcome

Loki’s main workflow implements and checks the requested change, then opens a pull request; a run that does not verify opens a draft.

Guide limitations

  • Claude Code is the default provider; the Anthropic API-key alternative is documented for the main loki start path.
  • A run may stop for a budget cap or end blocked, stalled or failed; inspect its outcome rather than assuming completion.
  • The receipt describes checks that ran and does not prove the code is bug-free.
Documentation 1 ↗
Source-based practical guide

Verify a run receipt locally

Check the signature and event-log consistency of the newest Loki run’s receipt.

Before you start

  • A Loki run with a receipt
  • Loki Mode installed in the environment used for verification

Steps

  1. Run loki verify to verify the newest run, or specify a run ID with loki verify .

  2. Treat exit code 0 as the verified result; consult the verification output and documented exit codes for other outcomes.

Expected outcome

Loki reports a verdict after re-hashing the receipt and checking its signature and event log.

Guide limitations

  • Verification checks the receipt and its recorded event log; it does not establish that the code is bug-free.
  • A receipt’s claims are limited to the checks it lists.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for AI coding assistance

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
Loki ModeSubmit a short task, PRD file or GitHub, GitLab or Jira issue for implementation.CLI, Self-hostedLoki Mode is distributed as a CLI with npm, Bun, Homebrew and Docker installation options. The README documents macOS and Linux support. Its primary workflow requires a model provider; Claude Code is the default, with an Anthropic API-key option for the main start path.
LlmcodeInspect a project's directory structure with `/tree`.CLIThe documented setup requires an API key and supports an API base URL and model setting. The project is open source under Apache-2.0.
Klaat CodeOpen a project directory for terminal-based coding assistance.CLI, ServerThe README provides a global npm installation command and documents browser sign-in with a KlaatAI account. It also identifies the repository as open source under Apache 2.0.
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
15 October 2026
Original website title
asklokesh/loki-mode · Official homepage title · retained in its source language
How we review sourcesSuggest a correction