Skip to content

Memmy v1.0.8

Choose a tag to compare

@github-actions github-actions released this 18 Aug 15:33
9450354

Memmy v1.0.8

Highlights

  • Made custom Agent onboarding more flexible with an optional conversation-history path and a simpler unified Agent selector.
  • Improved Memory reliability and responsiveness with safer desktop service recovery and parallel turn routing and recall.

Agent improvements

  • You can now provide a custom Agent's conversation-history file or directory when connecting it. If left blank, Memmy continues to discover the location automatically.
  • Combined preset selection and custom Agent naming into one keyboard-accessible field for a simpler setup flow.

Desktop improvements

  • Memory overview count cards now open their corresponding Memories, Policies, World Model, and Skills pages.
  • Added a locale-aware documentation link beside the Memory service status.
  • Improved recovery from stale or still-starting Memory service locks, reducing startup failures after an interrupted or abnormal shutdown.

Memory improvements

  • Turn routing and Memory retrieval now run in parallel, reducing avoidable waiting at the start of a turn while preserving routing evidence.
  • Memory service shutdown now closes the HTTP server and storage backend cleanly before releasing its database lock.

Packaging and reliability

  • Hardened Windows packages by validating the bundled native database modules for both Memory and Memmy Agent against the Windows x64 Electron runtime.
  • Hardened packaged runtime configuration and version-consistency checks across macOS and Windows.
  • Added packaged-runtime smoke checks and migration-state compatibility checks for existing v1 and current v2 upgrade state.

Downloads

Installation

On Windows, download the appropriate signed exe and run the installer. On Apple Silicon Macs, download the appropriate signed dmg, open it, and drag Memmy to Applications.

Checksums

Verify downloads with MD5SUMS.txt or SHA256SUMS.txt attached to this release. The workflow also verifies every OSS object against its Content-MD5 header before publishing.