Deploy or Connect
Mimir runs the Worker, storage, and private dashboard inside your Cloudflare account. Create that deployment once, then connect each additional machine.
Create a deployment
Section titled “Create a deployment”A fresh deployment requires a Cloudflare account, an OpenRouter API key, Node.js 22 with npm, and network access to npm and Cloudflare.
mimir setupSetup deploys the packaged Worker and dashboard, creates or reuses D1 and R2, applies migrations, registers this machine, and stores the OpenRouter key as a Worker secret. It does not require Bun, Go, or a source checkout.
For noninteractive setup, place OPENROUTER_API_KEY in the environment. Never
pass the key as a command argument or paste it into agent chat.
Connect another machine
Section titled “Connect another machine”Install Mimir on the new machine, then run:
mimir loginLogin authenticates through Cloudflare, discovers the deployment, registers a
fresh machine token, verifies /whoami, and saves the connection. It does not
need the OpenRouter key, Bun, Go, or dashboard build dependencies.
Connect directly
Section titled “Connect directly”When Cloudflare discovery is unavailable and you already have a Worker URL and machine token:
mimir setup --url https://mimir.example.workers.devInteractive setup reads the token through a secure prompt. Automation reads it
from MIMIR_TOKEN. This path does not require Wrangler or Node.js.
Activate a harness
Section titled “Activate a harness”Installed integrations must be loaded by their harness before capture begins:
| Harness | Activation |
|---|---|
| Pi | Restart Pi |
| Oh My Pi | Restart omp |
| OpenCode | Restart OpenCode |
| Hermes | Restart Hermes |
| Claude Code | Run /reload-plugins or restart Claude Code |
| Codex | Restart Codex |
| Cursor | Open or continue an agent session |
Run mimir doctor --json after activation. Resolve every failed check before
continuing to Verify Capture.