chat-recall-memorylisted

# Durable memory with chat-recall Two directions: **recall** what's already known, and **record** new facts so future sessions inherit them. ## Recall what's known - `mcp__chat-recall__recall_kg_query` — query an entity's relationships (facts with validity windows). `as_of: <date>` time-travels to what was true then. Use to VERIFY before asserting a fact ("did we decide to use Postgres?"). - `mcp__chat-recall__recall_kg_timeline` — chronological story of an entity (or everything). `mcp__chat-recall__recall_kg_stats` — graph overview. - `mcp__chat-recall__recall_wake_up` — high-importance facts + KG snapshot for a fast "what's true right now". - `mcp__chat-recall__recall_diary_read` — prior agent diary entries (narrative notes across sessions). `mcp__chat-recall__recall_get` — a scoped key/value. ## Record new knowledge (do this when something non-obvious is decided) - `mcp__chat-recall__recall_decision_record` — an explicit decision (subject, decision, reason, importance). Shows up in future wake-up context. Use the moment you and the user agree on something a later session would need. - `mcp__chat-recall__recall_kg_add` — assert a fact triple (subject → predicate → object, optional `valid_from`). E.g. `("chat-recall", "uses", "Postgres")`. - `mcp__chat-recall__recall_kg_invalidate` — mark a fact no longer true when a decision is reversed or a tool is replaced (keeps the graph honest). - `mcp__chat-recall__recall_diary_write` — narrative notes ("what