MemoryGuard

MemoryGuard

Governed shared memory for coding agents.

Local-first MCP memory with automatic organization, scoped rules, evidence, and rollback.

中文文档

Let agents write without turning shared memory into an unreviewed pile.

MemoryGuard organizes each write, preserves the evidence behind changes, and

keeps governance decisions reversible.

**No account. No remote server. No remote telemetry. Local-only usage telemetry

is optional and stores bounded, privacy-preserving aggregates locally.**

Quick start · Upgrade · Knowledge Library · Architecture · Supported hosts · Privacy and safety

A synthetic governed projection: signals move through memory categories while raw conversation text remains outside the graph.

What's New in v0.7.15

• Automatic CodeGraph builds: Trusted bootstrap starts a project's first build in a background process. Default and per-project switches persist; disabling automation preserves the graph. Supported file-write events trigger incremental refresh.
• Clear graph navigation: Switch between a file overview and symbols, filter by file, inspect neighboring relations, and use zoom controls.
• Bounded temporary storage: Ordinary graph queries read SQLite directly instead of retaining full-database copies. Validation and installation temporary files use the owning project/deployment cache and are cleaned up when the operation ends.

See the v0.7.15 release note and CodeGraph automation details. Reconnect or restart hosts after upgrading and repairing their provider integration.

Earlier governance improvements

v0.7.13 strengthens mandatory-rule replacement and recovery, improves audience-aware identity handling, and improves conflict resolution:

• Safe mandatory-rule replacement: Replacements validate the final mandatory package against audience matching, canonical rules, deduplication, sensitivity checks, and publication budgets. Equivalent unlocked predecessors retire in the same transaction; failed validation rolls back the complete update. See the replacement and recovery details.
• Native Agent/group audience matching: Matching and deduplication no longer split the same native audience solely by provider or runtime role. Distinct Agent identities remain separate, and project-scoped audiences retain their project boundaries. Provider repair uses the verified identity for its target provider.
• Readable, atomic conflict resolution: Conflict views preserve readable peer information, and resolution keeps peer groups intact while applying the selected changes atomically. Ambiguous conflicts remain unresolved.
• Cursor Hook protection: Cursor MemoryGuard Hooks now use a 30-second timeout, up from 15 seconds, with failClosed: true.

v0.7.14 only corrects release metadata for the GitHub repository rename; it does not change runtime behavior. See the v0.7.14 release note.

See the v0.7.13 release note and release history.

Earlier release details are kept in the Changelog and GitHub release records.

Token evidence and demo

Usage events distinguish measured_cached_input from measured_cache_write_input. measured_cache_coverage.cache_read and cache_write report complete, partial, or unavailable; measured zero remains 0, while missing provider data remains None/unavailable. Character-based estimates remain explicitly labelled estimated mg_deterministic_unit, never provider tokens.

Run the benchmark only against an authorized local workspace:

python scripts/benchmark_usage_telemetry.py --workspace . --window-days 7 --sync

Read the benchmark guide for measured, estimated, derived, and unsupported semantics. Use the demo recording checklist for a sanitized walkthrough. The repository's synthetic graph artwork is not a live product capture; it is not evidence of usage or savings.

Major V2 refactor in v0.6.0

v0.6.0 was a production data-plane refactor, not a storage-only upgrade:

• Authoritative V2 domains: Memory, Rules, Evidence, Content, Runtime, Projection, Assets, CodeGraph, Skills, and System state are separated into explicit SQLite domains with governed boundaries.
• Explicit cutover: V1_ACTIVE → V2_BUILDING → V2_READY → V2_ACTIVE is fail-closed; V2 never silently falls back to legacy stores or dual-writes after READY/ACTIVE.
• Lossless migration: frozen-source preparation uses coherent SQLite online backups, validates source/target evidence, rechecks live-source drift, and preserves V1 data plus migration backups for rollback.
• Native routing: MCP, CLI, GUI, and Hook surfaces are classified explicitly; the release closed the 233-surface cutover with 138 implemented routes, 95 retired routes, and zero neutral/blocker routes.
• Governed intelligence: Rule lifecycle and RuleMerge, extraction/enrichment, External MCP import, provider control-plane, conversation history, Knowledge Library, and GUI governance all use the V2 evidence and decision paths.
• Operational evidence: Reference Audit, per-domain SQLite health, guarded maintenance, rollback evidence, and safe unbound diagnostics are part of readiness and operations.

Why MemoryGuard

Persistent memory solves storage. It does not solve governance.

When several coding agents write into the same context, records become duplicated, stale, contradictory, over-broad, or unsafe to reuse. MemoryGuard sits between coding agents and their shared memory to keep that context usable.

System architecture

%%{init: {"theme":"base","themeVariables":{"background":"#071521","fontFamily":"Arial, sans-serif","fontSize":"14px","primaryTextColor":"#EEF4F8","lineColor":"#557287","edgeLabelBackground":"#071521","clusterBkg":"#0A1A29","clusterBorder":"#27445A"},"flowchart":{"htmlLabels":true,"curve":"basis","nodeSpacing":32,"rankSpacing":48,"padding":14}}}%%

flowchart TB Hosts["CODING-AGENT HOSTS Claude Code · Codex · Cursor · TRAE "]:::host Gateway["LOCAL INTEGRATION MCP stdio · redirect rules · lifecycle hooks "]:::gateway

subgraph Core["GOVERNANCE CORE "] direction LR Identity["TRUST identity · scope "]:::core MemoryAPI["MEMORY governed I/O "]:::active Rules["RULES scope · assignment "]:::rule HistoryAPI["HISTORY search · timeline "]:::history Security["SAFETY validate · quarantine "]:::danger

Identity --> MemoryAPI Identity --> Rules Identity --> HistoryAPI MemoryAPI --> Security end

subgraph Stores["LOCAL GOVERNED STORES "] direction LR SharedDB[("V2 DOMAIN STORES Memory · Rules · Evidence · Content ")]:::store HistoryDB[("HISTORY STORE isolated conversations ")]:::historyStore AuditDB[("RECOVERY STORE versions · receipts · backups ")]:::store end

Bootstrap["BOUNDED CONTEXT BOOTSTRAP mandatory rule pack · relevant recall "]:::bootstrap Control["HUMAN CONTROL CLI · desktop governance console "]:::surface

Hosts --> Gateway --> Identity MemoryAPI --> SharedDB Rules --> SharedDB HistoryAPI --> HistoryDB Security --> AuditDB SharedDB --> Bootstrap Control --> Identity

classDef host fill:#12243A,stroke:#38D5C8,color:#EEF4F8,stroke-width:1.4px; classDef gateway fill:#0D3338,stroke:#38D5C8,color:#EEF4F8,stroke-width:2.4px; classDef core fill:#12243A,stroke:#557287,color:#EEF4F8,stroke-width:1.4px; classDef active fill:#0D383A,stroke:#38D5C8,color:#EEF4F8,stroke-width:2px; classDef rule fill:#3B2C18,stroke:#F3B562,color:#EEF4F8,stroke-width:1.8px; classDef history fill:#102F45,stroke:#73C7F5,color:#EEF4F8,stroke-width:1.8px; classDef danger fill:#3A2028,stroke:#EA6A6A,color:#EEF4F8,stroke-width:1.8px; classDef bootstrap fill:#EEF4F8,stroke:#38D5C8,color:#071521,stroke-width:2.4px; classDef store fill:#0B1624,stroke:#7F96A8,color:#EEF4F8,stroke-width:1.4px; classDef historyStore fill:#102436,stroke:#73C7F5,color:#EEF4F8,stroke-width:1.4px; classDef surface fill:#EEF4F8,stroke:#38D5C8,color:#071521,stroke-width:2px;

style Core fill:#081827,stroke:#27445A,stroke-width:1px,color:#EEF4F8 style Stores fill:#081827,stroke:#27445A,stroke-width:1px,color:#EEF4F8 linkStyle default stroke:#557287,stroke-width:1.4px;

Quick start

MCP Registry metadata

This package exposes a local stdio MCP server as io.github.MerakOsiris/memoryguard. Registry metadata is kept in server.json, and the marker above ships with the PyPI package README. Releases are published through GitHub OIDC to PyPI and the official MCP Registry. Verify the current package version and the Registry entry's active/latest state through their live public records.

1. Install

python -m pip install agent-memguard

For the desktop governance console:

python -m pip install "agent-memguard[gui]"

2. Authorize the current project

memoryguard source add .

3. Connect or repair your coding agent

Global provider configuration is rebuilt from the real binding in the canonical user data home. The command is idempotent and removes superseded MemoryGuard project-level overrides after a successful global takeover.

# Repair one provider

memoryguard provider repair claude memoryguard provider repair codex memoryguard provider repair cursor memoryguard provider repair trae

#