@pify/memory

Persistent memory for pi: durable facts, project conventions, and a daily activity log — all plain markdown you can read, edit, and commit.

Part of the Pify suite. Install with pify install memory or pi install npm:@pify/memory.

What it does

• Two-tier markdown storage: global ~/.pi/agent/memory/ (MEMORY.md + daily/YYYY-MM-DD.md) for cross-project facts, and .pi/memory/MEMORY.md for per-repository conventions. Files are yours — read them, edit them, commit the project tier to git.
• Explicit learning: the agent saves when you ask ("remember that…") or when a correction should stick — via tools, never via surprise LLM calls at shutdown.
• Consolidation you asked for (v0.3): /memory consolidate <global|project|YYYY-MM-DD> hands the file to a model that merges duplicates and drops facts a later entry already corrected. It only ever proposes: the result is refused outright if it invents an entry that appears nowhere in the original, empties the file, or drops more than 60% of it; it passes the same secret gate as any write; you see a preview and confirm; and the previous content is kept as a recovery record, so /memory restore <id> puts it back.
• Real search, zero dependencies: BM25 full-text search through SQLite FTS5 via node:sqlite (built into Node 24+ and Bun); on Node 22 hosts it silently falls back to an in-process paragraph scan. Either way memory_search works out of the box.
• Secret gate: every write is scanned (AWS/GitHub/Slack/OpenAI/Google/npm keys, private key blocks, JWTs, api_key= assignments) and rejected with an explanation — credentials can never enter files that get re-injected into every session.
• Undoable forgetting: memory_forget writes a recovery record first; memory_restore <id> brings entries back.
• Cache-stable injection: memory is injected once per session as a hidden message before your first prompt (full MEMORY.md tiers capped + today/yesterday logs + an overview of the searchable archive) — the provider request prefix stays stable, so prompt caching keeps working. Measured, not asserted: bun run test/live/wire.mjs captures the real provider payload through before_provider_request and checks the marker reached the model, that it is not in the system prompt, and that the system prompt is byte-identical across runs (v0.4.1; technique from pi-code).
• Local-day discipline: daily logs are keyed by your local calendar day, not UTC.

Tools & command

Surface	What it does
memory_write	Save one entry to global / project / daily
memory_read	Read any memory file, or list daily logs
memory_search	FTS5/scan search across all memory files
memory_forget	Delete matching entries (writes a recovery record)
memory_restore	Undo a forget by recovery id
/memory	Status: file paths, sizes, active search engine
/memory search <query>	Search memory yourself, without asking the agent
/memory read <global|project|list|YYYY-MM-DD>	Print a memory file
/memory consolidate <global|project|YYYY-MM-DD>	Propose a merged, de-duplicated file (v0.3)

Migrating from pi-memory

@pify/memory uses the same on-disk layout as jayzeng's pi-memory, so your existing MEMORY.md and daily logs carry over untouched. The two register the same tool names and cannot run side by side — remove the old one first:

pi remove npm:pi-memory
pify install memory

License

MIT © Pify maintainers