Skip to content

MemoryGuard v0.7.6

Choose a tag to compare

View all tags
@MerakOsiris MerakOsiris released this 28 Aug 03:18
· 18 commits to main since this release
v0.7.6
42475c2

MemoryGuard v0.7.6

Released: 2026-08-28

v0.7.6 is a focused Codex Hook/MCP runtime reliability release. It keeps the
existing governance and lifecycle policy while making runtime selection,
concurrent state updates, and bootstrap failure state explicit and consistent.

Included

  • Codex lifecycle Hooks and the MCP server use the same content-keyed,
    immutable runtime snapshot. Installation no longer leaves MCP on one Python
    interpreter while lifecycle Hooks resolve another through PATH.
  • Hook session-state read/modify/write operations use short, re-entrant
    cross-process lock windows. A full Hook execution does not hold the state
    lock, so concurrent tools and sub-agent dispatch can proceed independently.
  • Bootstrap success writes a stable context hash and clears prior errors;
    bootstrap failures clear stale success state and record the applicable error.
  • Ordinary Stop capability, signature, dispatch, and runtime failures remain
    fail-open. A native response that explicitly reports mandatory-budget
    overflow is retained for the next tool call, which then fails closed.
  • The built-in Grok profile is discoverable from its installed user surface.
    Verified provider, CLI, and MCP metadata receive a stable program identity;
    generic or opaque values remain unresolved rather than being guessed.
  • The governance GUI follows the reference seven-page shell with persistent
    navigation, a central workspace, a context rail, readable Agent summaries,
    and family-aware icon fallbacks. Opaque technical IDs are kept in collapsed
    details instead of being the primary label.

Validation boundary

This release metadata records the Hook/MCP runtime fixes and their focused
regressions. Full-suite validation and external publication are performed by
the release workflow after the source changes are accepted.

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 both load the new snapshot.

Assets 2
Loading