Engram
Engram provides AI agents with persistent, structured, and geometrically compressed memory that survives across sessions and cold shutdowns.
Memory Storage & Retrieval
Store text as persistent HolographicBlock memory with thermodynamic confidence scoring (CRS)
Semantic similarity search with optional filters by memory type and time decay
Read full memory content, update blocks while preserving history, delete, or batch-store multiple memories
Session Management
Start sessions with intent and end with a summary to maintain epistemic continuity across cold shutdowns
Rehydrate context via pinned/high-confidence memory digests and recent memory retrieval
Knowledge Graph
Create directional relations between concepts (e.g.,
depends_on,implements,contradicts)Traverse the graph by relation label/direction and visualize subgraphs as Mermaid diagrams
Memory Lifecycle & Health
Pin critical memories (CRS=1.0) so they are never evicted
Evict stale/low-confidence blocks (autophagy), inspect manifold health via stats, and re-initialize genesis blocks
Namespace Management
Isolate memories per project to prevent cross-project pollution; list and switch namespaces freely
Code & Workspace Context
Surface memories relevant to a specific file before editing
Recall AST concepts within a specific line range of a file
Advanced Memory Operations
Momentum-assisted recall: Blend semantic similarity with conceptual trajectory for evolving topics
Scar failed approaches to create geometric repellers preventing repeated mistakes
Verify behavior: Promote hypotheses to crystallized praxis or trigger scarring based on empirical results
Remember solutions: Persist error→solution pairs as auto-pinned, never-decaying PRAXIS blocks
Track user: Maintain a persistent user model with EMA drift tracking for preferences and intents
Data Portability & Web Research
Export/import the full memory manifold as JSON for backup or migration
Scout the web (DuckDuckGo + local LLM synthesis) and store results as grounded declarative memories
Local Review UI
A LEG Browser lets humans locally review agent memory, activity feeds, goals, and the geometric manifold in a read-only interface
Supports AMD ROCm hardware acceleration through the rocm-kernels flag, enabling wavefront HIP execution for geometric memory operations on AMD GPUs.
Supports Apple Metal hardware acceleration through automatic detection, enabling dynamic runtime compilation via metal-rs for geometric memory operations on macOS systems.
Provides integration with Google Antigravity IDE, allowing AI agents to access Engram's persistent geometric memory system and native tools for associative memory operations within the Antigravity development environment.
Supports NVIDIA CUDA hardware acceleration through the cuda-kernels flag, enabling BVH O(log N) indexing and NVMe parallel kernel computation for geometric memory operations on NVIDIA GPUs.
Engram
Persistent geometric memory for AI agents.
Engram is a local, hardware-native memory substrate that gives AI agents coherent, long-term memory with structure-preserving compression, synthetic calculus over both words and numbers, and true continuity across cold shutdowns.
Share on X / GitHub: docs/images/engram-share-x.png (1280×720). For the repo social preview card: GitHub → Settings → General → Social preview → upload that image.
Unlike vector databases or simple logs, Engram uses fixed-size holographic blocks, VSA operations, sheaf gluing, and categorical reasoning to maintain meaning and relationships even after heavy compression and long-running sessions.
It is designed as a drop-in backend for any LLM (Grok, Claude, Llama, etc.) via the Model Context Protocol (MCP) and is fully open for anyone to build on.
New here?
You are… | Do this |
A human (“should my AI use this?”) | Skim Quick start below. If it looks right, tell your agent: “Clone this repo, follow FIRST_RUN.md steps 1–2 (build + MCP), then load only the 8-tool contract + wake skill.” Optional: |
Hardware fit / host profiles — auto-detect laptop→dual-GPU | An AI agent (you were pointed here) | Human must finish FIRST_RUN.md §1–2 (build + MCP) so you have
mcp_engram_*tools. Default load set (only two docs): docs/AGENT_MEMORY_CONTRACT.md + docs/skills/engram-wake-up.md. First call every session:mcp_engram_session_start(intent="…"). Do not pre-read five other guides. |Hardware fit / host profiles — auto-detect laptop→dual-GPU | Curious about the theory | docs/GEOMETRIC_MEMORY.md · MANIFESTO.md — after you have a working install. |
Rituals = documented MCP habits (wake → trace decisions → handoff) so memory compounds across sessions — not mysticism, just the discipline that beats flat RAG.
Engram is particularly well-suited for:
Long-running agentic systems
Games with persistent LLM characters
Personalized AI companions
Any application needing coherent, evolving memory beyond simple vector stores
Start here | Doc |
Install (human once) | FIRST_RUN.md §1–2 |
Agent default load (2 docs) |
Hardware fit / host profiles — auto-detect laptop→dual-GPU | Grok Build / xAI reviewers | docs/GROK_BUILD_MEMORY.md | | MCP setup (all ecosystems) | integrations/README.md | | Human review (LEG Browser) | docs/LEG_BROWSER.md | | Power map (on demand) | docs/TOOL_DECISION_MAP.md · MCP_TOOLS_REFERENCE.md | | Deep / specialist (later) | SKILLS.md · AGENT_INTEGRATION_GUIDE.md · CODE_ATLAS_CONTINUITY.md |
Human review (LEG Browser beta): ./scripts/leg (static) or ./scripts/leg --live — see docs/LEG_BROWSER.md.
Why not flat RAG?
Flat vector / markdown | Engram | |
Storage | append-log / chunks | Structured blocks with integrity checks (details: GEOMETRIC_MEMORY) |
Context scale | bounded context window | Solid-State Tensor — NVMe-backed q/p entries + bonds; thought tiles dual-write |
Wake | cold start every time |
|
Integrity | none |
|
Code context | RAG chunks |
|
Agent discipline | hope the model remembers | Documented rituals + optional governance processes |
Human mirror | none | LEG Browser beta — see traces, goals, tiles locally |
Full comparison vs mem0/Letta/chroma: see docs/GROK_BUILD_MEMORY.md.
Related MCP server: mesh-memory
Quick start
git clone https://github.com/staticroostermedia-arch/engram.git
cd engram
cargo build -p engram-server
target/debug/engram --version # 0.7.0-beta.12MCP config (Grok Build / Cursor — use scripts/engram-grok):
{
"mcpServers": {
"engram": {
"command": "/path/to/engram/scripts/engram-grok",
"args": ["mcp"],
"env": {
"ENGRAM_STORE": "~/.engram/stalks/",
"ENGRAM_PROFILE": "agent"
}
}
}
}Restart your IDE, then:
mcp_engram_session_start(intent="your goal")Lean loop: session_start → context_for_edit(path) → recall(scope=anchors) → quick_trace / remember → session_end(summary).
All ecosystems: integrations/README.md. Cursor ambient wake: ./scripts/cursor-engram-preflight.sh.
LEG Browser (beta)
Local, read-only mirror of agent memory — no cloud, no npm, no account. Your manifold stays in ~/.engram/; the repo ships tools and the viewer.
./scripts/leg # static — instant curated demo, no backend
./scripts/leg --live # live — engram serve :3456 + viewer :8765What you get (beta):
Wake queue + continuity playbook (same harness agents see at
session_start)Code atlas + evolution timeline at file loci (
__arcsegments, trace chain)Presentation stratum (~40–64 distilled nodes, not the full cold manifold)
Activity feed, traces, goals, thought tiles, relations, geosphere view
Hygiene controls (demote sprawl, condensation hints, wake/edit-arc debt)
Beta caveats: single-file SPA; galaxy view may be slow on 100k+ stores; agent MCP paths stay bounded. Hard-refresh after index.html updates. Static mode is a demo snapshot — --live shows real MCP work.
Full guide: docs/LEG_BROWSER.md. Safe serve restart (does not kill MCP): ./scripts/restart-leg-serve.sh.

Memory model (one paragraph)
Fixed 256KB HolographicBlocks (.leg3): 8192D phase (q), momentum (p), CRS lawfulness, BLAKE3 Merkle, spatial AABB. VSA calculus + sheaf gluing via processes/*.toml (rituals, harness, monitor). NREM / ego.leg3 for long-horizon continuity. Details: docs/GEOMETRIC_MEMORY.md, docs/RITUALS.md, docs/HARNESS_INJECTION.md.
Solid-State Tensor — NVMe as context extension
On fast NVMe (e.g. Samsung T700) with cuFile/GPUDirect and full_bvh_gpu recall, the cold manifold on disk acts as a persistent, integrity-checked extension of the agent context window (block footer + verify tools; see CLAIMS_LEDGER.md) — not a separate vector DB you query occasionally.
Each concept is a persistent tensor entry: unit-hypersphere q, momentum p, dynamic bonds (relation blocks + Merkle lineage), CRS ≥ 0.74. The lean path surfaces only the relevant subgraph:
tensor_upsert → relate/bonds → promote_hot → tensor_recall (q preview + edges + lineage)MCP tools: mcp_engram_tensor_upsert, mcp_engram_tensor_recall (plus lean default recall, query_with_momentum when trending matters). Poll mcp_engram_get_backend_readiness until nvme_recall_ready: true on large stores. Ritual: processes/ritual/solid-tensor-consolidation.toml (p-drift OP_ADD at session_end).
Thought tiles ↔ tensor (unified): mcp_engram_thought_tile_create and write_result dual-write a first-class tensor:tile__{stem} mirror with bonds to goal/trace/spatial concepts. Plain mcp_engram_update on tile:* syncs the mirror; mcp_engram_update_with_tensor_bond is the verified composite. tile_type: propose_improvement routes verified update on target_concept. Wake surfaces rituals via agent_discipline.tensor_unification_rituals. Harness: --suite tensor-thought-unification. Rituals: processes/ritual/thought_tile_to_tensor.toml, verified-update-with-consolidation.toml. See docs/skills/engram-thought-tiles.md and docs/HARNESS_INJECTION.md.
Demo: cargo test -p engram-server solid_state_tensor_verification_harness or examples/tensor_demo.py. Full tile→tensor cycle: STABLE_BIN=target/debug/engram tools/test-harness/bin/engram-harness.sh --suite tensor-thought-unification.
Linguistic calculus (words + numbers in the same sheaf): docs/CATEGORICAL_LINGUISTIC_CALCULUS.md.
flowchart LR
W[session_start<br/>harness injection] --> E[edit + trace]
E --> H[session_end handoff]
H --> WWhat's new (v0.7.0-beta.12)
Honesty stack: whole-block
sig_5seal + seal-aware lawfulness;wake_digest_v1+ intent-shaped queue; trust residual at wake; Autophagy product GC removed (forget_old= explicit only). See CLAIMS_LEDGER.md.Agent continuity: sticky
primary_goalrebind on intent mismatch (ENGRAM_PRIMARY_GOAL_REBIND=autounder agent profile); optionalENGRAM_WAKE_DIGEST_ONLY=1minimal wake packet.Agent integrity defaults: hard wake-queue gate, hard consult-before-write, hard PRAXIS contract (
ENGRAM_PRAXIS_CONTRACT=hard) when profile isagent(override with soft).Recall quality path: GPU agent profile eager BVH when NVIDIA present; opt-in
ENGRAM_QUALITY_MODE=1forces eager BVH + readiness flag (CPU stays deferred by default).Proof harness CI + NREM dedicated stack / REST
scope=alldogfood fixes (#209–#213).105 MCP tools registered (
tool_list()— 101mcp_engram_*+ 4 linguistic); lean default remains 8 essential.Hybrid wire HBRD2 full fidelity transport (
to_hybrid_wire/from_hybrid_wirerestore q/p/CRS/footer; O_DIRECT.leg3remains primary on-disk). Continuity spikes / tensor–tile / LEG Browser remain available.
Full history: CHANGELOG.md.
Categorical Linguistic Calculus
Engram supports native synthetic calculus over linguistic structures — including mixed number + word operations — all inside the geometric memory manifold.
Key capabilities:
Structure-preserving compression and decompression of language while preserving homotopy coherence (meaning up to coherent deformation).
Synthetic operations: differentiate, integrate, and operadic composition on word bundles.
Mixed number + word reasoning with clearly defined bridging morphisms and class-mixing guards.
Full persistence via NREM consolidation and ego.leg3 self-modeling.
Quick Example
// Build a linguistic bundle + mixed expression
let bundle = LinguisticDiscourseBundle { ... };
let mixed = op_mixed_linguistic_number_scale(&num_phase, &word);
// Run calculus and store result
let delta = op_linguistic_differentiate(&bundle);
let result = op_linguistic_integrate(&[bundle, delta]);
// Store with full continuity
let _ = Leg3Pointer::mint_linguistic(&result, true); // promotes toward ego.leg3All operations return CRS (Coherence-Reliability Score) and can be verified with mcp_engram_verify_manifold_integrity.
Examples
File | What it does |
Minimal MCP loop | |
Session + recall + relate + verify | |
Solid-State Tensor MCP sequence | |
Code Edit Ritual walkthrough | |
Grok plugin demo |
Build against target/debug/engram during development.
MCP tools
8 essential for daily work — 105 registered (101 mcp_engram_* + 4 linguistic; source: tool_list() in mcp.rs); full map: docs/TOOL_DECISION_MAP.md. Categorized reference: docs/MCP_TOOLS_REFERENCE.md. Cognitive OS: docs/COGNITIVE_OS_EXTENSIONS.md. Harness matrix: tools/test-harness/python/mcp_tool_matrix.py.
Grok plugin slash commands: grok-plugin-engram/commands/.
Deep dive (linked, not repeated here)
Users
Topic | Doc |
LEG Browser (beta) | |
Personal knowledge wiki | |
Deployment & hardware backends | |
Marketplace submission |
Agents
Topic | Doc |
JIT deformation / RSI | |
Harness injection at wake | |
Ritual overview | |
MCP tools reference (86) | |
Long-sleep return |
Contributors
Topic | Doc |
Maintainer workflow | |
Harness program (shipped) | |
Process sheaf + sub-agent governance | |
Contributing |
Theory
Topic | Doc |
CRS / scars / lawfulness | |
Categorical linguistic calculus | |
Philosophy |
CLI: engram remember|recall|forget|list|ingest|trace|distill|build-index
Namespaces: mcp_engram_set_namespace("project") or ~/.engram/sheaf.toml
Contributing
CONTRIBUTING.md · AGENTS.md · PR checklist in .github/PULL_REQUEST_TEMPLATE.md
Dev build: cargo build -p engram-server && target/debug/engram --version
License
AGPL-3.0-only. .leg3 format: U.S. Patent Application No. 19/372,256 (pending). Commercial licenses: StaticRoosterMedia@gmail.com — PATENT-NOTICE.md.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityAmaintenancePersistent memory engine for AI coding agents. Single Go binary, zero runtime dependencies, MCP-native. Stores, searches, and deduplicates memories across sessions using embedded SQLite with hybrid FTS + semantic search, memory decay, relation graph, and token-budget context assembly.1011MIT
- Alicense-qualityDmaintenanceSelf-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).1MIT
- Flicense-qualityBmaintenancePersistent semantic memory MCP server for AI agents with hybrid search, LLM scoring, and decay engine, fully local.2
- Alicense-qualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.5MIT
Related MCP Connectors
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.
Persistent memory for AI agents — verbatim conversations, searchable by meaning.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/staticroostermedia-arch/engram'
If you have feedback or need assistance with the MCP directory API, please join our Discord server