the product
Durable local continuity for AI agents.
Open source, local-first, model- and provider-agnostic. 15 Rust crates, signed releases, and a deliberately small MCP surface — stored on your machine, verifiable without a third party.
curl -fsSL "https://www.whitemagic.dev/install.sh?ref=product-a" | sh
No sudo required · Runs in user space (~25 MB) · glibc & musl
v9.2.1 · released September 20, 2026 · 15 crates · npm · Docker · MCP registry · MIT
No account · Memory and sessions stay on your machine · No usage telemetry off-device by default
the path
Install → Grimoire → Connect → Work → Resume.
Five steps, in the order people actually run them.
- 01
Install
curl -fsSL "https://www.whitemagic.dev/install.sh?ref=product-step" | shOne line on Linux x86-64 (install-gated). macOS and Windows binaries are published; they are not yet install-gated.
- 02
Grimoire
wm grimoireChecks the host, verifies the substrate, proves restart continuity, and reports five separate readiness facts instead of one green badge. Add --write (or run wm connect --write) to actually patch detected client configs.
- 03
Connect
wm servePoint a standards-compliant MCP client at the local server — wm connect wires detected clients; wm setup <client> writes one config.
- 04
Work
Use your agent normally. Memories, sessions, and checkpoints are written locally as you go; governance and provenance run at the dispatch seam, not as prompts.
- 05
Resume
"where did we leave off?"In a new session — or after a crash, upgrade, or model switch — the checkpoint, its rationale, and its source come back from the local store.
Setup guide: ask your AI, first run, your data, client config →
why continuity
Context windows reset. Work does not.
WhiteMagic gives AI agents durable local memory, session continuity — and governance, provenance, and preservation — all running on your own hardware, governed by your explicit policies, and auditable without a third party. Open source under MIT, verified by over 4,777 public tests, and built in the open with signed releases.
Ask normally in conversation. Your agent handles WhiteMagic through MCP behind the scenes. Continuation is lossless: session replay is byte-exact and excludes private records, and opted-in cold discovery reaches archived memories without thawing them.
The practical difference: an agent that can recover a decision, its rationale, and its source does not need the whole history re-explained. Context cost drops because memory carries the state, not the transcript.
where data lives
Your disk, your rules.
The store lives under your home directory (under 1MB after init — measured 2026-09-15; LMDB maps are sparse). No memory, prompt, or session content is transmitted off-device, and no usage telemetry is sent off-device by default. Local diagnostic telemetry may be recorded on-device for self-observation; the only sharing path is the optional install-funnel report, explicit opt-in and off by default (`wm telemetry enable --share` prints the exact payload first; reset-id rotates its random identifier). Release/update checks contact GitHub only when run, and work offline. Stores are not encrypted by default, and deleting a store directory does not remove backups, exports, replicas, or other project stores — inventory those copies first.
Backup/export a galaxy and restore it anywhere; a restored store is re-verified before it is trusted.
supported clients
Designed for standards-compliant MCP clients.
The server runs locally; the client list is a documentation list, not an integration matrix. Each name links to its setup entry in the guide.
the MCP surface
One meta-router, nine lifecycle tools.
Model-, IDE-, and provider-agnostic: the memory lives on your disk, so switching agents never loses your history.
Registry routes are not all public surface: authored capabilities compress to curated routes, then to tools/list lifecycle entrypoints, then to one adaptive wm meta-router (PRAY).
tools/list: wm · memory.create · memory.search · memory.read · memory.list · memory.hybrid_recall · session.record · session.continuity · session.start
verify it yourself
Ready when you are — not when we say so.
Readiness without the single green badge
wm grimoire reports five separate facts instead of one boolean: substrate ready, agent wired, continuity verified, semantic recall available, fully activated. “The substrate works” and “you are connected to it” are different claims, so they stay separate.
release channel & support
Open alpha — a channel, not a milestone.
The version number is a compatibility signal; the release channel is an evidence claim. WhiteMagic v9.2.1 ships on the open alpha channel — beta and stable are earned by their exit conditions, never assigned by a version bump.
- Current minor
- Security and bug fixes, on the install-gated Linux x86-64 line.
- Previous minor
- Security fixes.
- Older minors
- Archival — no fixes. macOS and Windows binaries are published in every release but are not install-gated and are not supported.
Support policy in full: SECURITY.md
backup & uninstall
Leaving is as supported as staying.
Backup / export — galaxies export and import as portable artifacts; a restored store is re-verified before it is trusted. Seals (HMAC-SHA256 manifests) can be re-checked against off-store snapshots.
Uninstall — remove the binary and the store directory. Removing a configured store does not remove backups, exports, replicas, or other project stores, and does not establish secure erasure; inventory those copies first.
v9.2.1 — what changed
Mesh authority, opt-in telemetry, and at-rest groundwork
- —Admission fix found by benchmarking: code-heavy content (HTML/jQuery, hex-color lists, formatted snippets) is admitted again, and memory.batch_create skips and reports bad items instead of voiding the whole batch.
- —Backup integrity: envelope.json is covered by the backup SHA256 manifest, so tampering with a backup's label is detected at restore instead of displayed.
- —At-rest record sealing, dark by default: with WM_AT_REST_MODE=keyfile|passphrase, record bodies seal under the galaxy key; wm at-rest migrate seals existing stores with a crash-safe ledger, wm doctor discloses counts without resolving the key, and mode off stays byte-identical. No crypto-erasure claim until the later slices.
- —Search can no longer be killed by a bad limit: limit 0 used to reach the index engine and panic the server process; limits are validated at the tool boundary (minimum 1 in the schema) and guarded in the engine.
- —Session record contract: out-of-range importance is rejected instead of silently clamped, turn_type must be one of the documented values, blank content is refused, and the CLI rejects NaN or out-of-range importance.
- —Retrieval truth and cost: a BM25-ranked search discloses recall_mode bm25, the rerank pool is decoupled from the candidate width (measured: R@1 58.0 with a small pool at about a fifth of the embedding cost), and a BM25-weighted search skips the query embed entirely.
- —Governance and first-run polish: the command guardrail no longer demands confirm for prose handoff fields (arrows and numeric comparisons are not commands), mesh-key and read-only-index warnings fire only where actionable, and wm contract --check prints its success line.
- —Install and release: the installer gained checksum-verified macOS targets (arm64/x86_64) while Windows stays refused, and site guide commands are verified against the released binary before every tag.
- —Boundary and threat model: a machine-checked dispatch boundary matrix (direct/wrapper/NLU/autonomous/federated × authority/effect gates) and the confidentiality/injection threat model are documented.