pi-hermes-memory v0.9.5
This patch release strengthens persistent-memory reliability, makes background maintenance work correctly with active Pi context and custom providers, and makes search-to-mutation workflows safe and unambiguous. It is fully compatible with existing memory files and configuration.
Highlights
- Background review and session flushing now carry the active working directory and model into their child fallback process, improving support for custom and local OpenAI-compatible providers. Direct reviews resolve credentials through Pi’s public
ModelRegistry.getApiKeyAndHeaders()API instead of version-sensitive internal state. - Memory maintenance is safer under real-world concurrency: recovery snapshots are bounded by count and UTF-8 byte budget, FTS index migrations coordinate across Pi processes, and cancellation watchdogs remain active until cleanup completes.
- Memory searches now show both the logical scope and the exact mutation target required by
memory_replaceandmemory_remove. Pasted search results remain valid mutation lookup text, including project names with special characters.
Fixed
- Added configurable automatic-consolidation failure warnings (
autoConsolidationWarnOnFailure) and treat a session reload/replacement during consolidation as a deferred retry rather than a failed operation. (#165, #171) - Preserved full-entry replacement semantics so partial matches cannot silently remove sibling facts or metadata. (#170)
- Bounded retained recovery snapshots, including the case where a single snapshot exceeds the total retention budget. (#172)
- Select the newest relevant failure records for legacy failure injection. (#173)
- Improved CJK memory search with an FTS5 trigram index and safe short-query handling; migration is now robust when multiple Pi processes start together. (#174)
- Route background review, correction, and flush facts explicitly to global, project, or failure memory, preventing project facts from leaking into global memory. (#176)
- Apply overflow grace per memory target so automatic consolidation does not interfere with active agent work across unrelated scopes. (#177)
- Ensure shutdown flush follows Pi’s awaited lifecycle contract and child fallback review receives the active model/provider context.
- Make mutation errors identify the valid target(s), including project-scoped failure memory, rather than asking the model to guess. (#180)
Upgrade notes
No migration or configuration change is required. Existing MEMORY.md, USER.md, project, failure, and SQLite memory data remain compatible.
Full comparison: v0.9.4...v0.9.5
Thanks to everyone who reported these edge cases and helped improve the extension for the community.