Skip to content

Persistent Memory 1.1.0 — Smarter setup for your machine

Choose a tag to compare

View all tags
@vshcherbukhin vshcherbukhin released this 07 Sep 14:40
v1.1.0
497bde3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Persistent Memory now helps you choose an embedding setup your computer can support. Smaller machines can use OpenAI or Voyage embeddings while keeping the memory database, graph, and dashboard local.

What is new

  • Resource-aware installation: compare actual RAM, free RAM, disk space, CPU, and Docker resources with minimum and recommended budgets. Setup blocks installation below the minimum.
  • Models that fit: suggest a suitable local Ollama model or API embeddings; disable local models when even the smallest option cannot fit. An 8 GB M2 Mac can use API embeddings and API fact extraction when the remaining requirements pass.
  • API embedding choices: OpenAI text-embedding-3-small (value default) or text-embedding-3-large; Voyage voyage-4, voyage-4-large, or voyage-4-lite. Voyage uses its own key. Connection tests check provider access and vector dimensions.
  • Safer retries: check image runtimes and compiled modules, build serially, and attempt one targeted rebuild/pull after an image check fails. Disk-full and storage I/O failures stop with guidance.
  • Careful cleanup: remove unused artifacts with proven installation ownership; preserve persistent data, images used by other containers, and shared artifacts whose ownership is unknown.
  • Protected settings: preserve saved keys and existing embedding configurations; allow a failed first-install configuration change only when the database is proven empty.
  • Concurrent-operation fixes: prevent separate wizard tabs from changing settings or loading models during installation and resource tests.
  • Clearer documentation: requirements tables, Windows browser GPU guidance, and explanations of GitHub Releases and Packages.

Install or update

Read the requirements and model guide and installation instructions. API embedding requests send memory/search text to the selected provider.

Existing public 1.0.0 installations can use the supported updater from their checkout:

npm run update-persistent-memory -- --branch master

In Windows PowerShell, use npm.cmd. The updater takes recovery snapshots and preserves existing credentials, memories, volumes, and embedding configuration. Changing an existing corpus to another embedding model requires a separate re-embedding migration. Update checks remain automatic; installing an update remains explicit.

Validation and limits

Root typechecks and test suites passed, together with 426 installer tests, 202 dashboard tests, 17 isolated desktop/narrow-browser wizard checks, and release/documentation validation. Independent reviews covered resource safety, concurrency, upgrade metadata, and the publication payload.

Physical macOS installation, real paid-provider connections, and deliberate Docker-storage corruption were not tested for this release. Resource budgets are planning estimates. Image rebuilding cannot repair a damaged Docker data disk or database. The new image preparation/repair flow applies to installation and retries; upgrades retain the existing updater recovery path.

This is a source release: ZIP and tar.gz downloads are available below. The installer builds Docker images locally. No npm package, prebuilt GHCR images, or standalone Windows/macOS executable is included.

Full release history · Changes since v1.0.0 · Release PR #3

Assets 2
Loading