Correct a stale AI memory with its source in view

A receipt is evidence of origin, not current truth

Cairn.ink Memory's hosted recall_memory result can include a Memory id and a source receipt. The receipt helps you see what was said when the note was created. It cannot tell you whether a later code change or policy made the note outdated.

This flow uses Cairn.ink Memory's hosted tools, which every MCP client and the Claude Code plugin can call. Hosted MCP exposes remember_memory, recall_memory, and forget_memory; it does not expose a correct_memory tool. The local open-source layer has a different tool surface, documented separately.

Replace a stale note deliberately

1. 1. Recall and inspect

   Call recall_memory with a narrow query. Read the exact Memory and receipt, and verify the current fact against a maintained project source.

2. 2. Forget the exact old id

   If the statement is wrong, use forget_memory with the exact memory_id returned by recall_memory. Content-based or bulk deletion is not supported. Check the tool result before continuing.

3. 3. Save a verified replacement

   If a durable private note is still useful, explicitly call remember_memory with the corrected wording and a source excerpt that contains no secrets. Treat it as a new Memory, then inspect the returned receipt.

The web view and the local preview

When the feature and the Memory's capabilities are enabled for your account, Cairn's “What I know about you” pane on the map can show source receipts and offer edit or forget actions. The separate Settings → Memory page controls recall preferences; it is not the Memory editor.

For local preview behavior, including its inspect_memory and correct_memory tools, follow the public open-source guide. Those local tools and their setup are separate from the hosted MCP tools described here.

What you should see

A successful forget result identifies the exact Memory and says it will no longer be recalled. A separately successful save returns a new id and receipt. You can make another narrow recall to check what is returned, but search results alone are not a deletion audit.