Results for “memory-poisoning”

Stores, retrieves, and curates persistent facts in a structured memory map, distinguishing between user facts and reference text.

Persists and recalls agent knowledge across sessions using four approaches: static KB, company wiki, persistent memory, and session brain.

Structured memory system with domains, decay, and links for AI agents, replacing flat memory files with a weighted, interconnected memory palace.

Consolidates auto-memory files in ~/.claude/projects by auditing, planning, and executing a 4-phase cleanup with user approval.

Provides persistent, compounding memory for AI agents across sessions using local markdown files, with optional Supabase-backed semantic search.

Retrieve task-relevant project and global memory without loading everything. Load when the user asks what we decided, recall prior context, find memory about a feature, explain past rationale, resume a task, or check deferred ideas.

Indexes document metadata in SQLite and manages ephemeral key-value state in Redis for cross-session context.

4-layer recall procedure (durable → semantic → PostgreSQL → daily notes) before claiming "no context". Invoke when user explicitly asks "do you remember", "what did we discuss about X", "search history". NOT a general assistant — only fires when recall is the explicit task. Drop the prior "use proactively" rule. Triggers: "do you remember", "what did we discuss", "when did", "find that conversation about".