Skip to content

Releases: 3vilM33pl3/memory

v0.5.3

19 Apr 08:57
b57e052

Choose a tag to compare

Dev stack isolation

  • New Profile::{Prod,Dev} in AppConfig auto-detected from current_exe() (cargo target/ ⇒ dev), overridable via MEMORY_LAYER_PROFILE=dev|prod.
  • Dev profile is fully independent of the installed stack: its own service endpoint, sockets, runtime paths, and — now — database. Global config is ignored in dev.
  • memory dev init scaffolds .mem/config.dev.toml and .mem/runtime/dev/. Interactive prompt (or --copy-from-global / --no-copy-from-global) offers to seed the overlay with shared settings (database URL, LLM/embedding endpoints, features, writer identity).
  • TUI header shows [dev] when on the dev profile so overlapping dev and prod TUIs are distinguishable.

TUI performance

  • Idle CPU drops from ~60–70% to single digits via dirty-flag drawing: terminal.draw only fires when state changes or once per second.
  • event::poll raised to 500 ms, agent snapshot worker to 5 s, manager status worker to 10 s.
  • Event::Resize now explicitly triggers a redraw instead of being silently swallowed.

New memory types and remember flag

  • MemoryType gains User, Feedback, Project, Reference variants for cross-conversation knowledge.
  • memory remember --type <kind> overrides automatic classification.

Fixes

  • Shift+Tab navigates to the previous TUI tab again.
  • resolve_agent_repo_root skips gracefully when the agent session's cwd is gone.
  • Managed-watcher spawn sites prefer the repo-local .mem/config.toml so the watcher joins the same service the TUI uses.
  • memory dev init walks ancestors to find .mem/, so running it inside a git worktree writes the overlay to the main repo.
  • Agent rate-limit filter respects the selected session type.

Refactor

  • Watcher owner-exit detection uses kill(pid, 0) instead of polling a full mem-agenttop snapshot each tick; drops the mem-agenttop dependency from mem-watch.

v0.4.4

08 Apr 14:43
5f9f7f1

Choose a tag to compare

Republished v0.4.4 from the latest main commit to include the Linux warning fix for memory service run.\n\nRelease commit: 5f9f7f1\nPrevious v0.4.4 release/tag replaced.

v0.4.3

08 Apr 10:14
84465b8

Choose a tag to compare

Highlights

  • split the Memory Layer repo-local skill into a bundled setup with an umbrella memory-layer skill plus focused memory-query-resume, memory-plan-execution, and memory-remember skills
  • updated memory init, memory wizard, and packaged installs so they bootstrap the full skill bundle under .agents/skills/
  • refreshed the developer and wizard docs to describe the new bundled skill layout and routing

Verification

  • cargo test -p mem-cli -p mem-service -p mem-watch
  • npm --prefix web run build
  • ./packaging/build-deb.sh
  • dpkg-deb --info target/debian/memory-layer_0.4.3_amd64.deb

v0.4.2

02 Apr 15:21
006b49b

Choose a tag to compare

Full Changelog: v0.4.1...v0.4.2

v0.4.1

01 Apr 10:47
50d22c9

Choose a tag to compare

Full Changelog: v0.4.0...v0.4.1

v0.4.0

30 Mar 22:30
3392bed

Choose a tag to compare

Memory Layer 0.4.0

This minor release includes the recent resume and TUI responsiveness improvements, including:

  • actionable resume briefings that focus on underlying project work rather than Memory Layer activity noise
  • non-blocking Resume tab loading with background prefetch when a checkpoint exists
  • much faster backend /overview and /resume paths
  • continued support for watchers, bundles, multiple embedding spaces, and shareable project memories

Verification

  • cargo test -p mem-cli -p mem-service -p mem-watch
  • npm --prefix web run build
  • ./packaging/build-deb.sh
  • dpkg-deb --info target/debian/memory-layer_0.4.0_amd64.deb

v0.3.1

30 Mar 18:27
3993c69

Choose a tag to compare

Memory Layer v0.3.1

Highlights:

  • Plan-approval checkpoint workflow added to the Memory Layer skill
  • TUI startup renders immediately instead of showing a blank screen
  • Resume tab briefing layout is fixed
  • Backend handoff now waits for the Cap'n Proto TCP port to clear during replacement

Verification:

  • cargo test -p mem-cli -p mem-service -p mem-watch
  • npm --prefix web run build
  • ./packaging/build-deb.sh
  • dpkg-deb --info target/debian/memory-layer_0.3.1_amd64.deb

v0.3.0

30 Mar 17:49
2033992

Choose a tag to compare

Memory Layer v0.3.0

Highlights:

  • Resume briefings with checkpoint-based project re-entry
  • Project memory bundle export/import in the CLI and web UI
  • Parser-backed repo analyzers for Rust, TypeScript/JavaScript, and Python
  • TUI startup and resume rendering fixes
  • Backend handoff fix for clean repo-local mem-service restarts

Verification:

  • cargo test -p mem-cli -p mem-service -p mem-watch
  • npm --prefix web run build
  • ./packaging/build-deb.sh
  • dpkg-deb --info target/debian/memory-layer_0.3.0_amd64.deb

v0.2.0

26 Mar 17:44
54a15a3

Choose a tag to compare

Memory Layer 0.2.0

Highlights:

  • multi-space embeddings so switching embedding models does not overwrite older vectors
  • reembed now materializes the active embedding space, with explicit prune-embeddings cleanup
  • README and user docs improved around vector search, writer configuration, and embedding operations

Verification:

  • cargo test -p mem-cli -p mem-service -p mem-watch
  • ./packaging/build-deb.sh
  • dpkg-deb --info target/debian/memory-layer_0.2.0_amd64.deb

v0.1.5

25 Mar 18:33
172fa16

Choose a tag to compare

Memory Layer v0.1.5

Highlights:

  • web UI served directly by mem-service
  • relay mode for services that cannot reach PostgreSQL directly
  • writer identity support for multi-writer projects
  • pgvector-backed semantic retrieval and related-memory ranking improvements
  • commit history sync as searchable project evidence
  • richer query and activity diagnostics in the TUI
  • restructured user and developer documentation

Upgrade notes:

  • existing installs upgrading to semantic retrieval need PostgreSQL pgvector enabled and then should run mem-cli reindex --project <slug>
  • write-capable workflows now need a configured writer.id or MEMORY_LAYER_WRITER_ID