MemoryOS

Overview

MemoryOS is a vendor product (by Iwo Szapar) that adds persistent local memory to AI coding agents — Claude Code, Codex, and compatible workspaces. Instead of relying on chat history, it stores structured state in a local SQL database of 14 queryable collections, kept either on the user’s laptop or in their own Supabase project.

Key Facts

• Persistence model: local SQL database (14 collections), not chat history — user controls storage location (laptop or own Supabase)
• Health scoring: a “brain health” score across setup/usage/fluency dimensions; free tier includes a 45-check health scan and 7 context-engineering pattern scores
• Transport: built on model-context-protocol as its standardized connection layer
• Setup: single npx terminal command; the free scanner makes zero network calls and reads only file structure/configuration, not code or documents
• Paid features: confidence-scored knowledge storage, alias-expansion full-text search, decision logging, and decay detection that flags stale information
• Pricing (vendor-stated): free health check; Standard $199/year;Pro$349/year (adds monthly updates, priority support)

Relationships

• “belongs-to” agent-memory-systems — memory-first family: local persistent store consolidated across sessions rather than a browsable wiki artifact
• “uses” model-context-protocol — connection layer between the agent and the memory store
• “is-sibling-of” redis-iris-agent — both are 2026 vendor-preview memory-first products bundling a persistent store with a diagnostic/observability layer (health scoring vs. auto-generated data-retrieval tools)
• “differs-from” mem0 — mem0 is an open-source (60.6k⭐) production memory library; MemoryOS is closed, paid, coding-agent-specific, and bundles a health-scan product on top of the memory store

Implications

MemoryOS’s decay-detection and confidence-scored storage are a commercial, single-agent-tool-scoped version of the same problem this vault’s own [[memory-lifecycle]] concept addresses (staleness flagging, confidence signals) — evidence that “flag stale facts automatically” is converging into a product category, not just a vault-governance idea. Because the source is a self-promotional vendor page with no independent review or repository link, the pricing and “20+ hrs/week” customer claim should be treated as vendor-stated, not verified.

Open Questions

• No public repository or independent review found in the captured source — cannot verify the health-scan methodology or the decay-detection algorithm.
• How does the “brain health” scoring compare to this vault’s own wikilint checks (provenance floor, staleness, orphan detection)?

External Links

• Product page: https://www.iwoszapar.com/memory-os

Sources