/memory — store a fact in the knowledge base
Usage:
/memory <fact>
Action:
- Take everything after the
/memoryprefix and its following space as the fact text. - Call the MCP tool
kb_rememberwith:text: the fact, verbatimsource:"chat"(it came from a direct user instruction)
- Reply:
Remembered: <fact>so the user has confirmation.
If kb_remember returns an error, surface it verbatim — do not fabricate a fallback. The most common cause is the host-side Postgres being down; the user will know to check.
Examples:
/memory Sarah Chen prefers email over phone calls.→kb_remember(text="Sarah Chen prefers email over phone calls.", source="chat", entities=["Sarah Chen"])/memory My DBS account number is …→ store, but never echo the value back on subsequent recalls.
When you can extract structure cheaply, do — pass entities=[...] for named people/places/orgs, tags=[...] for topical keywords. They make /recall better. Don't over-engineer it.