v0.0.48 pi-v0.2.0
vadimdemedes/inkOct 1, 2026 → Oct 1, 20260 days between releases
What's New
Pi-native memory tools now require explicit project ownership validation to prevent conflicts.
Breaking Changes
- Pi-native mem_update and mem_delete require an explicit expected_project argument
- Pi startup no longer silently imports tracked .engram/manifest.json chunks
New Features
- mem_context now accepts optional max_bytes and compact arguments
- mem_session_end validates the host session ID before processing
- Automatic prompt capture redacts <private> blocks before truncation
- Servers launched by the plugin now have Cloud autosync enabled by default
- Resumed sessions register with resume: true
Improvements
- Background-capture warnings are now displayed in the owning Pi UI instead of raw stderr
- TypeBox dependency is removed in favor of Pi's built-in wildcard peer
- pi-engram init preserves existing MCP server configurations and removes the need for the external adapter
Bug Fixes
- Explicit cross-project project or cwd saves use an isolated, project-owned session instead of conflicting with the current session's ownership
Upgrade Notes
Update your code to pass the expected_project argument to mem_update and mem_delete methods. Run engram sync --import from the checkout to import tracked chunks that were previously imported silently. Remove the mcpServers.engram entry manually and reload Pi if you were relying on the old adapter.
The Two Releases
v0.0.48
Oct 1, 2026· 21 days ago
Introduces a unified design for the Node.js and Python SDKs, allowing users to create and run robots with a single object call. The SDKs now share a common API for scraping, extraction, and crawling operations.
Full release notesgentle-engram v0.2.0
Oct 1, 2026· 21 days ago
Pi-native memory tools now require explicit project ownership validation to prevent conflicts. The `pi-engram init` command preserves existing MCP server configurations and removes the need for the external adapter.
Full release notes