Install Anvil
A single self-contained binary (~22–27 MB). No runtime required — nothing to install beyond Anvil itself. Optionally install QMD for persistent cross-session context and memory.
Current release: v2.2.19 — seven platforms • SHA256 verified • shell completions included • self-updating via anvil upgrade
Install on macOS
brew install culpur/anvil/anvilcurl -fsSL https://anvilhub.culpur.net/install.sh | bashanvilIntegrity — what the installer actually verifies
Every binary is published with a SHA256 checksum at two independent origins so a compromise of one does not forge the other:
- Primary:
anvilhub.culpur.net/sha256/<binary>.sha256 - Fallback:
github.com/culpur/anvil/releases/download/vX.Y.Z/<binary>.sha256
The installers — install.sh and install.ps1 — and anvil upgrade try the primary first, fall back to GitHub, and refuse to install on dual failure. An unverified binary never lands on disk.
Using Anvil
Launches the TUI. First run walks through provider setup, optional Ollama model selection, and saves your config.
Authenticate with a specific provider. Supports anthropic (OAuth or API key), openai, google, xai, ollama.
One-shot prompt — print the answer and exit. Great for scripting or CI.
Resume your most recent session, restoring context and conversation history.
Start the REPL on a specific model. E.g. anvil model claude-sonnet-4-6, anvil model qwen3:8b, anvil model gpt-4o.
Self-update to the latest release. SHA256-verified against the anvilhub.culpur.net manifest; aborts on mismatch.
Prints an install health checklist — binary version, dependencies (QMD, git, node), PATH, shell completions.
Re-run the first-run wizard. Use this to change provider, reconfigure Ollama, or reset defaults.
Remove the binary and shell completions cleanly. Vault data in ~/.anvil is preserved.
QMD — optional knowledge-base engine
QMD indexes your codebase, documentation, and past sessions so Anvil can inject relevant context into every conversation. It is optional — Anvil runs fine without it — but recommended if you want memory that spans sessions.
1. Install QMD
The Anvil install script installs QMD automatically when Node.js 18+ is present. To install it manually:
2. Index your project
Point QMD at the folders you want it to see. Glob patterns are supported.
3. Keep the index fresh
QMD does not run as a background daemon — it operates on a local SQLite + embedding index that Anvil queries directly. Re-run qmd update && qmd embed whenever you want the index to pick up new files, or set up a periodic refresh:
For a lighter-touch setup, just run qmd update manually when you start a session. The index is on local disk — nothing leaves your machine.
Anvil auto-discovers QMD
Anvil probes for the qmd binary at startup (on $PATH, plus the standard install paths for each OS). When it finds QMD, it polls every 30 seconds for index health and surfaces the status on the rail's MEMORY block alongside the seven memory layers. Anvil also auto-registers a per-session collection for ~/.anvil/history/ and runs qmd update in the background so newly-archived session files become searchable without manual re-indexing.
If qmd is not installed, Anvil silently falls back to its in-process memory layers. There is no error, no warning — QMD is strictly an enhancement.
Use QMD from inside Anvil
QMD also ships an MCP server so you can call it as a tool from any session. Anvil's MCP host wires it up automatically when present:
Learn more: github.com/tobi/qmd
Troubleshooting
'anvil' command not found after install▾
SHA256 verification failed during install▾
PowerShell: 'running scripts is disabled on this system'▾
Permission denied when running the binary▾
Ollama models don't appear in /model▾
Shell completions aren't working▾
How do I roll back to a previous version?▾
Is FreeBSD ARM64 or OpenBSD supported?▾
Having trouble? Check GitHub Issues or browse skills on AnvilHub.
Learn more about Anvil →