Skip to content

MemoryGuard v0.7.8

Choose a tag to compare

View all tags
@MerakOsiris MerakOsiris released this 29 Aug 08:15
· 15 commits to main since this release
v0.7.8
0b64cd4

MemoryGuard v0.7.8

Release target: 2026-08-29

v0.7.8 consolidates the governance and observability work prepared after
v0.7.7. It keeps the local-first, evidence-first, fail-closed boundaries and
does not claim CI or PyPI success before the release workflow reports it.

Included

  • Canonical reads and writes converge related rules, habits, and memories while
    retaining source links, evidence contributions, graph branches, supersede
    history, conflict decisions, and reversible settlement receipts. Mandatory
    context has an independent character/token budget; count warnings do not
    silently truncate storage or injection.
  • Agent discovery and governance use verified, stable program identities and
    readable labels. Shared-group scope, automatic decisions, risk explanations,
    stale-conflict closure, and safe family-aware icons are available through the
    seven-page GUI information architecture. Technical IDs remain available in
    details for audit without being the primary user-facing label.
  • Optional usage telemetry records local MCP conversion events and host-reported
    token measurements in .memoryguard/usage_telemetry.sqlite. The Token page
    supports seven- and thirty-day windows and shows the measurement basis. The
    savings ratio is an estimate from deterministic MemoryGuard units, not a
    provider billing result. Current host token measurements cover Codex and Grok;
    Claude, Cursor, and Trae are explicitly reported as unsupported.
  • Codex lifecycle reclamation is gated by verified terminal/deleted thread
    evidence and does not treat an ordinary turn boundary as conversation close.
    Installed provider repair aligns MCP and lifecycle Hooks to the current
    interpreter while preserving Agent/shared-group identity and conservative
    fail-closed repair behavior.

Privacy boundary

Telemetry is local-only. It does not upload data and does not store conversation
bodies, account names, raw source paths, or instance identifiers. Remote model or
embedding operations remain explicit opt-in behavior described in the README.

Upgrade

python -m pip install --upgrade agent-memguard
memoryguard --version
memoryguard doctor

After upgrading a Codex installation, repair the provider binding and restart
the Codex host so the MCP server and lifecycle Hooks load the aligned runtime.

Validation boundary

This document does not assert CI, wheel, or PyPI publication success. Those
results must be recorded from the release workflow and package checks after the
source and documentation gates complete.

Assets 2
Loading