Ports the OpenClaw "search before answering" protocol to the Cursor and Claude plugin surfaces so the agent reads the palace before answering about past work, people, projects, or prior decisions instead of guessing from model memory. - integrations/shared/recall-protocol.md: single source of truth for the recall protocol, referenced by the skill and the rule so they cannot drift. - skills/mempalace-recall/SKILL.md: recall-only skill (the mempalace skill keeps setup/mine/status); cross-linked from the ops skill. - rules/mempalace-recall.mdc: plugin recall rule, alwaysApply: false so it only fires on recall-relevant turns and never adds MCP latency to greenfield work. - examples/cursor/rules/: opt-in copies for non-plugin users, including an aggressive alwaysApply: true variant documented with its latency tradeoff. - .claude-plugin/skills/mempalace-recall/SKILL.md: Claude plugin parity. - tests: assert the recall skill and rules/ discovery layout; the shipped rule must be alwaysApply: false. - docs: .cursor-plugin/README.md and the cursor-hooks guide now describe the three layers of recall (hook + skill + rule). The Antigravity plugin mirror lands as a follow-up on the antigravity branch, where .antigravity-plugin/ exists. Co-authored-by: Cursor <cursoragent@cursor.com>
24 lines
1.1 KiB
Plaintext
24 lines
1.1 KiB
Plaintext
---
|
|
description: When the user asks about past work, prior decisions, people, projects, or events that may be filed in MemPalace, call mempalace_search (or mempalace_kg_query for relational or time-bound facts) before answering from model memory. Return stored content verbatim; never guess when the palace might know.
|
|
alwaysApply: false
|
|
---
|
|
|
|
# MemPalace recall
|
|
|
|
Before answering anything that may already be in the user's memory
|
|
palace — past work, prior decisions, a person, a project, or "what did
|
|
we do / decide / discuss last time?" — search the palace first:
|
|
|
|
1. Call `mempalace_search` with a short keyword query. Use
|
|
`mempalace_kg_query` for relational or time-bound facts.
|
|
2. Quote the drawer's **verbatim** text. Never summarize or paraphrase
|
|
stored content.
|
|
3. If results are empty, say so — do not invent an answer. If the MCP
|
|
server is unavailable, surface the error; do not fall back to guessing.
|
|
|
|
Skip recall for pure greenfield work with no memory relevance (renaming
|
|
a variable, fixing a typo). Recall is question-driven, not reflexive.
|
|
|
|
Full protocol: `integrations/shared/recall-protocol.md`. Deeper guidance:
|
|
the `mempalace-recall` skill.
|