irisxc4/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:
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.