The personal agent operating system
Branch any audit point.
Recover any client to a known-good state.
No detail is ever overwritten.
I · The well of memory
Today, the well has new water. Every action your agents take, every read, every write, every halt — sealed in a tamper-evident chain at the root of the World Tree, retrievable forever. Mimir is the supervisor that lives on your VPS. He spawns specialist agents on demand, learns from their work, and lets you replay or branch any decision they ever made.
You supervise Mimir. Mimir supervises the team.
II · Three runes
Fork any audit point at datom granularity. Try a different decision in a parallel timeline; commit only the branch that wins.
mimir branch \
--agent watcher-7af1 \
--from chain://event-1247
Re-execute any decision deterministically. Intervene at any step. Watch the trajectory change exactly where you change it.
mimir replay \
--agent watcher-7af1 \
--from chain://event-1247 \
--intervene tool=write_file
Produce an EU AI Act Article 12 evidence package signed end-to-end with Ed25519. Hand it to the regulator. They can verify it without you.
mimir export \
--format=eu-ai-act \
--from 2026-05-01 \
--to 2026-08-01
Hermes-agent (Nous Research, 129K stars) supports only /undo and cannot do any of these without a substrate rewrite. Letta, Mem0, and AnythingLLM have memory but no audit chain. Cursor, Cline, and Aider have neither.
III · The six branches
mimir spawn --tier SAFE creates a child agent under your authority with bounded skills, a vault tier, and a capability token.
Successful patterns are distilled into reusable skills, gated by replay byte-identity, audit-chain integrity, score delta, and stub coverage.
Children sharing state commit atomically — either both ship or neither does. Software- transactional memory at the substrate.
Spawn N children to try N approaches. Score them. Commit only the winner. The N−1 losing branches leave zero trace.
PUBLIC, SAFE, SENSITIVE, PII — capability tokens enforced server-side. A SAFE-tier child literally cannot read PII, even if it tries.
Every spawn, every read, every write, every halt — one Ed25519-signed datom in a Merkle-chained log spanning the whole fleet.
IV · The trunk
Mimir is built on persistence-os — a bitemporal, effect-typed substrate where every fact is an immutable datom, every action is an effect, every plan is an EDN AST, every shared state change is a transaction, every LLM boundary has a spec, and everything is REPL-live.
Open-core under AGPL-3. Substrate completion shipped at v0.8.5a1 with 2135 tests passing.
Substrate on GitHub →V · Drink at the well
The OSS tier is the funnel. The Compliance tier funds the development. Everyone drinks from the same well.
Everything below. Run the Docker image on your VPS or laptop. Forever.
Hosted Ed25519 retention (90d), email support, multi-device sync, web UI.
Shared memory graph, RBAC, team audit dashboard, 1y retention.
EU residency, ISO mapping, expert-witness export, dedicated tenant, SLAs, SSO.
VI · The install
Once v0.1.0 ships, paste this into Claude Code. It will provision Mimir on your VPS, mint your Ed25519 keys, wire your MCP, and start the agent loop. 90 seconds, end to end.
Alpha targets July 2026. Tell me where to send the install command.
One email when alpha ships. No newsletter.