The setup guide now has its own page. Open the installation guide →
the product
WhiteMagic gives local AI clients a durable memory layer they can use to preserve project context and resume work. The stable Gen 2 core is open source and runs on your hardware; optional hosted services are separate.
Use it when an agent needs to carry decisions, project notes, and next actions across sessions, context resets, or client restarts. It is a local memory layer, not a hosted model or a replacement for your coding assistant.
The published browser example checks the signatures and digests of a receipt bundle locally. It demonstrates record-integrity checks, not that its sample events happened.
Try a browser receipt check →The canonical local memory and session records stay on your device by default. No account or hosted service is required for the local core. Your connected AI provider controls content sent through its client; optional hosted services have separate data handling.
Read data and privacy details →The stable runtime exposes a compact MCP lifecycle surface and documented setup for supported clients. Client setup is documentation checked, not a claim of a tested integration matrix.
See client setup →Three Entrances · Architectural Triad
repo: whitemagic
Run the standalone binary on your machine. Connect to Claude Code, Cursor, or any MCP client via stdio to preserve decisions across restarts.
repo: continuity-receipt
Causal Provenance Receipts (CPR) provide Ed25519 signed audit trails aligned with IETF SCITT and AER drafts. Verifiable offline.
repo: mandalaos-gate-lite
Deterministic kernel sandboxing via Linux Landlock LSM, strictly bounding filesystem and socket permissions before agent tool execution.
Isolation Architecture · Zero Egress
The WhiteMagic core runs as a local child process. Connected AI clients communicate strictly over stdio JSON-RPC. Context and indexes remain isolated on local disk with zero external telemetry.
Claude Code / Cursor / Codex
Landlock LSM + Policy Gate
LMDB / SQLite / CPR Receipts
Release Generations · Capability Comparison
| Capability | Gen 2 Stable (v9.3.4) | Gen 3 Preview (v10.7.0) |
|---|---|---|
| Primary Focus | Daily-use default, mature & tested | Kernel-level security & compact workflows |
| Storage Engine | LMDB (~/.local/share/whitemagic) | Multi-backend (SQLite / RocksDB / Gen3 Store) |
| Security Confinement | Standard OS process isolation | Linux Landlock LSM hardware-enforced sandbox |
| Routing Surface | 30 lifecycle tools (curated) | Expanded mesh & evaluation surface |
| Workflow Syntax | Natural language JSON-RPC | Sutra compact glyph parser |
release & evidence
This catalog describes the stable Gen 2 runtime, v9.3.4. The experimental Gen 3 preview has a separate tool surface.
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).
wm · memory.create · memory.search · memory.read · memory.list · memory.hybrid_recall · session.record · session.continuity · session.start · memory.update · memory.revisions · session.checkpoint · memory.ingest · receipts.emit · receipts.verify · memory.count · memory.stats · memory.tags · memory.aggregate · memory.associations · memory.batch_read · memory.query · memory.filter · memory.nearby · memory.vector.search · session.list · session.recall · session.replay · gnosis.status · gnosis.explain
The version and platform claims below come from independent channel release records. Gen 2 is the stable daily-use default. Gen 3 is an experimental preview; its source development status and test results do not certify every published installer or host.
This changelog belongs to stable Gen 2, independently of the Gen 3 experimental preview.
Read the stable changelog ↗Release artifacts and signatures are published beside each channel record. Receipts prove integrity and authorship, never truth: what a signature establishes, how to verify one in five minutes, and the browser explorer all live on the trust page.
release artifacts and signatures ↗trust receipts →verification explorer →
ways to explore
Start with the workflow you already have. These small comparisons can help you see whether local memory adds useful continuity.
proposed experiment
Keep document retrieval where it is. Try WhiteMagic for project decisions and checkpoints, then ask a fresh session to recover one decision and its rationale.
proposed experiment
Keep your current notes workflow. Import a few non-sensitive project notes and see whether a new session can answer one continuity question.
proposed experiment
Try one task across two clients or models. Note what carries over, what is lost, and which release and configuration you used.
These are ideas to try, not verified adapters or performance promises. Record the WhiteMagic release channel, configuration, baseline, real task, observations, and reproduction steps.
Gen 3 · experimental architecture
Gen 3 explores peer exchange, compact workflow expressions, pressure-aware regulation, and signed evidence. These source capabilities have separate qualification limits and do not describe the stable Gen 2 default.
Peer exchange · experimental
The Gen 3 mesh source implements signed peer messages, TCP synchronization, and portable record bundles. Source and local tests do not establish independent multi-host deployment, WAN latency, or production network isolation.
Workflow expressions · experimental
The Sutra module defines a glyph vocabulary and a parser for compact workflow expressions. Parsing a supported expression does not establish loss-free preservation of natural-language intent; compression and end-to-end performance require separate evaluation.
Resource regulation · experimental
The homeostasis module represents memory pressure, latency, errors, and context use, and selects regulation regimes. Model fields and local tests do not establish autonomous reasoning quality or production self-regulation.
Signed evidence · published and proposed
Published Causal Provenance Receipts use Ed25519 over canonical JSON. A design note proposes hybrid post-quantum profiles; no released CPR post-quantum profile or SCITT interoperability is established here.