memory-layer

What problem does it solve?

It solves the problem of losing valuable decisions, bugfixes, patterns, and project context between Pi sessions, forcing you to repeat research and re-diagnose issues from scratch.

Core Features & Use Cases

• Remembers across sessions: Persistently stores observations such as decisions, bugfixes, constraints, and discoveries in a local SQLite database.
• Smart recall and context injection: Searches with hybrid ranking (FTS relevance × recency × trust × recall history) and injects the most relevant memories into new sessions while prioritizing architecture and key work.
• Code and doc intelligence: Indexes code symbols and Markdown docs (tree-sitter AST via WASM and native doc section/link/glossary extraction) so you can retrieve both memory and the underlying source context.
• Trust scoring and dedup: Deduplicates similar saves, updates in place by ID, soft-deletes stale memories, and adjusts trust based on code changes.

Quick Start

Use memory-layer to search for what you previously decided about a specific component by running: memory search for "how we handle session recovery" in your project.