WhiteMagic Labs
Give your AI agent memory between sessions.
Keep project notes, decisions, and next actions for the next session, restart, or client. WhiteMagic is an open-source memory layer that runs on your hardware.
The local core is MIT licensed and needs no account or cloud. Optional hosted services are separate.
1. Install on your machineStable Gen 2 v9.3.4
curl -fsSL "https://www.whitemagic.dev/install.sh?ref=home-quick-install" | sh -s -- --version v9.3.4 --dir "$HOME/.local/bin" --ref home-quick-install2. Choose your client to connect it
Installer and direct downloads
a practical workflow
Keep the next session connected to this one.
WhiteMagic stores records your MCP-connected client can save and retrieve. Start with a small project and check what carries over.
01
Save what matters
Ask your connected client to record a project note, a decision and its reason, or a session checkpoint.
02
Open the next session
Restart or switch to another configured client using the same local store. Your saved records remain available.
03
Recall and continue
Ask the client to retrieve the relevant records. Review the context it recovers, then continue the work.
> User: Continue from where we left off.
call session_continuity(limit: 1)
[Checkpoint #423495 · Commit 6fe795a]
Done: release audit passed, checksums verified against published manifest.
Next queue: 1) Update /trust compliance crosswalk; 2) Draft STF grant milestones.
> Assistant: Context recovered. Let's proceed with queue item #1: compliance crosswalk.
Engineering teams & air-gapped deployments: Enforce Zero-Egress DLP and Landlock capability sandboxing across local coding agents.
Explore Enterprise Scopes →channels and evidence
Separate channels, separate records.
Stable remains the default install choice. The experimental preview has its own version, binary, and store path. Each release record belongs to its own channel.
- Stable channel · Gen 2
- v9.3.4 · default install recommendation
- Experimental channel · Gen 3
- v10.7.0 · preview (Landlock sandboxing & Sutra)
- Local core
- runs and stores locally by default
- Telemetry to WhiteMagic
- the local core sends no off-device usage telemetry by default
optional hosted service
Try hosted recall without a local install.
Generate a free evaluation key, then connect your client using the hosted setup instructions. Hosted recall is separate from the memory store on your device.
Free evaluation key · 50 recalls/day
No account or payment needed. Generate a key, or use your existing key in the configuration below, to search the read-only public corpus.
.mcp.json — or: claude mcp add --transport http whitemagic-hosted https://mcp.whitemagic.dev/mcp --header "Authorization: Bearer YOUR_KEY_HERE"
Replace YOUR_KEY_HERE with your key before using this configuration.
{
"mcpServers": {
"whitemagic-hosted": {
"type": "http",
"url": "https://mcp.whitemagic.dev/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY_HERE"
}
}
}
}before you start
A few useful answers.
What does WhiteMagic add to my AI client?
A local store for project notes, decisions, and session checkpoints. An MCP-connected client can save and retrieve those records so a later session has context to continue. The local core runs on your hardware and needs no account.
See the product and its boundaries →Where does my data live?
In a local store under your home directory by default. The default store is not encrypted. Backups and exports are separate copies, and deleting a store folder does not establish secure erasure. The setup guide explains storage, backup, and optional protection.
Read the storage guidance →What can leave my machine?
The WhiteMagic local core keeps its memory and session records on your device, with no usage telemetry off-device by default. Optional local diagnostics stay on-device unless you enable the install-funnel sharing option. Your connected AI client and provider control the content they send; optional hosted services process requests you send to them. Release and update downloads also need a network connection.
Read the data and privacy details →What evidence can I inspect?
The current release record, v10.7.0, reports 1,657 tests passed, 10 ignored, and 0 failed. Current release facts come from the signed release records; individual test results link to dated reports. Stable Gen 2, experimental Gen 3, and hosted services have separate evidence. Source CI, a local test, and a production service result establish different things.
Inspect the evidence and its limits →How do I connect an agent?
Install the stable channel, choose your client in the setup guide, then run its first-session check. WhiteMagic speaks MCP locally over stdio. The guide provides platform-specific commands, client configuration, and separate experimental-preview instructions.
Open client setup →How the lab works
Publish evidence and failures, keep the local core independent, and design around people's choices.
Read the six operating rules
Label every claim
A measurement, an observation, a guess, and an ambition are four different objects. Each is tagged as what it is, and a claim that cannot point at its source is rewritten or dropped.
Keep the core on your hardware
The default install is a local binary and a local store. Networked conveniences may arrive later, but nothing in the core depends on them, and the local path is not a degraded demo.
Observation earns enforcement
Nothing that throttles, blocks, or isolates is trusted before it can show a measured false-positive rate. Watching first is a governance position, not just an engineering step.
Portability over lock-in
Memory sits in documented formats on your disk. Changing model, provider, editor, or machine is a configuration change — the history does not come along as a migration crisis.
Design for both sides of the table
People and agents will share this work. Usability, consent, attribution, and accountability are inputs to the design, not outside costs discovered after launch.
Publish the losses
Evaluations are built so the lab's own software can finish behind, and failures are documented next to wins. A result that cannot embarrass the lab is not treated as evidence.
your next step
Start with the stable local core.
The setup guide takes you from installation to a first connected session, with separate instructions for the experimental preview.