Skip to content

Memmy v1.1.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Sep 06:20
v1.1.3
1807e3a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Memmy v1.1.3

Fixes

  • Fixed packaged Memory startup and restart on Windows and macOS. Memmy Desktop now starts its bundled Memory runtime directly, avoiding Windows scheduled-task permission failures and macOS service-manager restart races.
  • Fixed Memory viewer restart after quitting Memmy Desktop. Background Memory can reload its configuration and restart its service after the Desktop connection has closed, including repeated restarts.
  • Desktop now upgrades older Memory runtimes that it owns to the bundled version after existing migrations finish and database locks are released. Compatible standalone installations and newer runtimes are preserved.
  • Fixed Linux CLI release builds selecting an older branch when a branch and release tag share the same name.
  • Custom BYOK models outside the built-in capability catalog can now receive image inputs instead of being treated as text-only. Models explicitly marked as text-only retain the existing fallback.
  • Account-based Memory summaries now use the dedicated summary model, including legacy configuration migration.
  • Windows Memory background services now use a hidden launcher with file logging, preventing a persistent command window during login and service restarts. Task definitions preserve Unicode paths, and ending the scheduled task also stops its Memory child after a short cleanup window. Existing launchers are refreshed during installation, start, and compatible-runtime reuse. A denied update to an old scheduled task no longer blocks Desktop from using or starting Memory.

Upgrade Notes

  • Memmy Desktop and Agent are version 1.1.3. The bundled Memory service, viewer, and memmy-memory CLI use the independent version 2.1.1.

  • Memory continues running after Desktop exits unless Stop Memory when quitting is enabled. Standalone Memory CLI installations retain their operating-system service management.

Fixes

  • Fixed Memory startup and restart issues in the Windows and macOS installers. The desktop client directly manages the Memory provided with the package, avoiding conflicts between Windows scheduled task permission errors and macOS system service restarts.

  • Fixed an issue where Memory could not restart from the viewer after exiting the desktop client. Memory can still reload its configuration and restart the service after the desktop connection is lost, supporting continuous restarts.

  • The desktop client will upgrade its managed runtimes to the included version after the old Memory has completed migration and released the database lock; it retains compatible standalone installations and newer versions.

  • Fixed an issue where the build would retrieve the old branch when the version branch and tag name were the same when releasing the Linux CLI.

  • Custom BYOK models can now accept image input even when they are not included in the built-in capability directory; models explicitly marked as supporting only text will still use the original rollback method.

  • Memory summaries in account mode now use a dedicated summary model and are compatible with old configuration migrations.

  • The Windows Memory background service now uses a hidden launcher and writes logs to a file to avoid leaving a command window when logging in and restarting the service. Task definitions are compatible with Chinese paths; after ending a scheduled task, its Memory child process will stop after a brief window cleanup; the old launcher will be updated when installing, starting, or reusing existing compatible runtimes. When an old scheduled task fails to update due to insufficient permissions, it will no longer block the desktop client from using or starting Memory.

Upgrade Notes

  • The desktop client and Agent version is 1.1.3; the Memory, viewer, and memmy-memory CLI included with the package are upgraded independently to 2.1.1.

  • When "Stop Memory on Exit" is not enabled, Memory continues to run in the background after exiting the desktop client. The separately installed Memory CLI retains the system service management method.

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. Before creating the Draft, the workflow verifies Normal OSS objects with Content-MD5 and Multipart objects with OSS CRC-64/XZ.

Assets 15
Loading