Loki Agent 𖤍

Loki Agent | Loki Desktop

The self-improving AI agent built by WunderCorp, Inc.. It's the only agent with a built-in learning loop — it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions. Run it on a $5 VPS, a GPU cluster, or serverless infrastructure that costs nearly nothing when idle. It's not tied to your laptop — talk to it from Telegram while it works on a cloud VM.

Use any model you want — OpenRouter, OpenAI, your own endpoint, and many others. Switch with loki model — no code changes, no lock-in.

Quick Install

Linux, macOS, WSL2, Termux

curl -fsSL https://loki.computer/install.sh | bash

Windows (native, PowerShell)

Heads up: Native Windows runs Loki without WSL — CLI, gateway, TUI, and tools all work natively. If you'd rather use WSL2, the Linux/macOS one-liner above works there too. Found a bug? Please file issues.

Run this in PowerShell:

iex (irm https://loki.computer/install.ps1)

The installer handles everything: uv, Python 3.11, Node.js, ripgrep, ffmpeg, and a portable Git Bash (MinGit, unpacked to %LOCALAPPDATA%\loki\git — no admin required, completely isolated from any system Git install). Loki uses this bundled Git Bash to run shell commands.

If you already have Git installed, the installer detects it and uses that instead. Otherwise a ~45MB MinGit download is all you need — it won't touch or interfere with any system Git.

Android / Termux: The tested manual path is documented in the Termux guide. On Termux, Loki installs a curated .[termux] extra because the full .[all] extra currently pulls Android-incompatible voice dependencies.

Windows: Native Windows is fully supported — the PowerShell one-liner above installs everything. If you'd rather use WSL2, the Linux command works there too. Native Windows install lives under %LOCALAPPDATA%\loki; WSL2 installs under ~/.loki as on Linux.

After installation, the first-run quick setup uses OpenRouter by default. Create an API key at openrouter.ai/keys, then choose your model when prompted.

source ~/.bashrc    # reload shell (or: source ~/.zshrc)
loki              # start chatting!

Troubleshooting

Windows Defender or antivirus flags uv.exe as malware

If your antivirus (Bitdefender, Windows Defender, etc.) quarantines uv.exe from the Loki bin folder (%LOCALAPPDATA%\loki\bin\uv.exe), this is a false positive. The file is Astral's uv — the Rust Python package manager Loki bundles to manage its Python environment. ML-based antivirus engines commonly flag unsigned Rust binaries that download and install packages.

To verify your copy is authentic:

# Install GitHub CLI if needed
winget install --id GitHub.cli

# Login to GitHub
gh auth login

# Run verification
$uv = "$env:LOCALAPPDATA\loki\bin\uv.exe"
$ver = (& $uv --version).Split(' ')[1]
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$zip = "$env:TEMP\uv.zip"
Invoke-WebRequest "https://github.com/astral-sh/uv/releases/download/$ver/uv-x86_64-pc-windows-msvc.zip" -OutFile $zip -UseBasicParsing
gh attestation verify $zip --repo astral-sh/uv
Expand-Archive $zip "$env:TEMP\uv_x" -Force
(Get-FileHash "$env:TEMP\uv_x\uv.exe").Hash -eq (Get-FileHash $uv).Hash

If attestation says "Verification succeeded" and the last line prints True, you're good.

To whitelist Loki:

• Windows Defender: Run PowerShell as Admin → Add-MpPreference -ExclusionPath "$env:LOCALAPPDATA\loki\bin"
• Bitdefender: Add an exception in the Bitdefender console (Protection > Antivirus > Settings > Manage Exceptions)
• Whitelist the folder, not the file hash — Loki updates uv and the hash changes every version

For more context, see the upstream Astral reports: astral-sh/uv#13553, astral-sh/uv#15011, astral-sh/uv#10079.

Getting Started

loki              # Interactive CLI — start a conversation
loki model        # Choose your LLM provider and model
loki tools        # Configure which tools are enabled
loki config set   # Set individual config values
loki config get   # Print individual config values
loki gateway      # Start the messaging gateway (Telegram, Discord, etc.)
loki setup        # Run the full setup wizard (configures everything at once)
loki claw migrate # Migrate from OpenClaw (if coming from OpenClaw)
loki update       # Update to the latest version
loki doctor       # Diagnose any issues

📖 Full documentation →

CLI vs Messaging Quick Reference

Run loki for the terminal UI, or start the gateway and talk to Loki Agent from Telegram, Discord, Slack, WhatsApp, Signal, or Email. Once you're in a conversation, many slash commands are shared across both interfaces.

For the full command lists, see the CLI guide and the Messaging Gateway guide.

Documentation

All documentation lives at doku.sh:

Migrating from OpenClaw

If you're coming from OpenClaw, Loki can automatically import your settings, memories, skills, and API keys.

During first-time setup: The setup wizard (loki setup) automatically detects ~/.openclaw and offers to migrate before configuration begins.

Anytime after install:

loki claw migrate              # Interactive migration (full preset)
loki claw migrate --dry-run    # Preview what would be migrated
loki claw migrate --preset user-data   # Migrate without secrets
loki claw migrate --overwrite  # Overwrite existing conflicts

What gets imported:

• SOUL.md — persona file
• Memories — MEMORY.md and USER.md entries
• Skills — user-created skills → ~/.loki/skills/openclaw-imports/
• Command allowlist — approval patterns
• Messaging settings — platform configs, allowed users, working directory
• API keys — allowlisted secrets (Telegram, OpenRouter, OpenAI, Anthropic, ElevenLabs)
• TTS assets — workspace audio files
• Workspace instructions — AGENTS.md (with --workspace-target)

See loki claw migrate --help for all options, or use the openclaw-migration skill for an interactive agent-guided migration with dry-run previews.

Contributing

We welcome contributions! See the Contributing Guide for development setup, code style, and PR process.

Quick start for contributors — use the standard installer, then work from the
full git checkout it creates at $LOKI_HOME/loki-agent (usually
~/.loki/loki-agent). This matches the layout used by loki update, the
managed venv, lazy dependencies, gateway, and docs tooling.

curl -fsSL https://loki.computer/install.sh | bash
cd "${LOKI_HOME:-$HOME/.loki}/loki-agent"
uv pip install -e ".[all,dev]"
scripts/run_tests.sh

Manual clone fallback (for throwaway clones/CI where you intentionally do not
want the managed install layout):

Create the venv outside the cloned source tree — a venv inside the directory
the agent operates from can be wiped by a relative-path command the agent runs
against its own checkout, destroying the running runtime mid-session.

curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv ~/.loki/venvs/loki-dev --python 3.11
source ~/.loki/venvs/loki-dev/bin/activate
uv pip install -e ".[all,dev]"
scripts/run_tests.sh

Community

• 💬 Discord
• 📚 Skills Hub
• 🐛 Issues
• 🔌 computer-use-linux — Linux desktop-control MCP server for Loki and other MCP hosts, with AT-SPI accessibility trees, Wayland/X11 input, screenshots, and compositor window targeting.

License

MIT — see LICENSE.

Built by WunderCorp, Inc..