v0.3.23 pi-v0.2.0
NandhaKishorM/layaOct 1, 2026 → Oct 1, 20260 days between releases
What's New
Pi-native memory tools now require explicit expected_project arguments for updates and deletes.
Breaking Changes
- Pi-native mem_update and mem_delete now require an explicit expected_project argument.
- mem_session_end now only accepts the current Pi host session ID and rejects foreign IDs.
- Pi startup no longer silently imports tracked .engram/manifest.json chunks.
New Features
- mem_context now accepts optional max_bytes and compact arguments.
- Automatic prompt capture redaction for private blocks.
- Explicit cross-project usage now creates isolated, project-owned sessions.
Improvements
- pi-engram init preserves existing MCP server entries instead of replacing them.
- Background-capture warnings now appear in the Pi UI instead of raw stderr.
- Session resumption improvements allow resumed sessions to register with resume: true.
Bug Fixes
- mem_session_end now correctly validates the session ID before processing.
- Pi startup behavior regarding .engram/manifest.json chunks is now explicit.
Upgrade Notes
Update all mem_update and mem_delete calls to include the expected_project argument. Run engram sync --import if your workflow relies on tracked manifest chunks. Ensure mem_session_end commands use the current session ID.
The Two Releases
v0.3.23
Oct 1, 2026· 21 days ago
Enhances MCP tool support, adds Swedish language detection, and fixes ONNX quantization defaults. Also introduces Docker checkpoint baking from ModelScope and security documentation.
Full release notesgentle-engram v0.2.0
Oct 1, 2026· 20 days ago
Pi-native tools now require explicit `expected_project` arguments for memory updates and deletes. The `pi-engram init` command preserves existing MCP server entries, and Pi startup improvements enhance session resumption and prompt capture.
Full release notes