undeadindustries
24ad98df8c
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>
Cursor IDE Hooks — Example hooks.json Files
Sample configurations for wiring the MemPalace Cursor hooks into the
Cursor IDE. These are examples only — they are intentionally not
placed at the repo root (/.cursor/hooks.json) because Cursor
auto-loads project-level hooks from any trusted workspace, and the
repo is regularly opened by contributors. We do not auto-arm hooks on
contributor checkout.
Variants
hooks.json — full (recommended)
Three hooks wired:
sessionStart— callsmempal_wake_hook_cursor.sh, which returnsadditional_contexttelling the agent to recall scoped to the wing inferred from the workspace root. Cursor-only — Claude Code has no equivalent.stop— callsmempal_save_hook_cursor.sh. Counts stop invocations per conversation and emits afollowup_messageeveryMEMPAL_SAVE_INTERVAL(default 15) telling the agent to file the session into the palace and write a diary entry.loop_limit: 1is defense-in-depth on top of our own loop-count check.preCompact— callsmempal_precompact_hook_cursor.sh. Runsmempalace minesynchronously on the transcript before compaction summarises it, then drops a marker so the nextstopforces a save followup.
hooks.minimal.json — stop only
Lightest install. Wires just the save hook. Use this if you don't want the sessionStart recall context or the preCompact transcript snapshot.
How to use
The $HOME placeholder is not expanded by Cursor — you must
substitute the absolute path before saving the file. Pick one:
Option A — let install.sh do it
Project scope — writes <repo>/.cursor/hooks.json:
hooks/cursor/install.sh --scope project --target /path/to/your/repo
User scope — writes ~/.cursor/hooks.json, applies to every Cursor workspace:
hooks/cursor/install.sh --scope user
The installer copies the hook scripts to ~/.mempalace/hooks/cursor/,
substitutes the absolute paths, and merges the entries into your
existing hooks.json without clobbering unrelated hooks. See
install.sh --help for --dry-run, --uninstall, and --variant.
Option B — copy + edit manually
- Copy the chosen example to the target location:
- User scope:
~/.cursor/hooks.json - Project scope:
<your-repo>/.cursor/hooks.json
- User scope:
- Replace every
$HOMEwith the absolute path to your home directory (e.g.,/Users/youor/home/you). - Make sure each hook script is executable
(
chmod +x ~/.mempalace/hooks/cursor/mempal_*_hook_cursor.sh). - Restart Cursor, or wait for it to auto-reload the file.
Why aren't these files at the repo root?
Cursor automatically loads .cursor/hooks.json from any trusted
workspace. Placing a real hooks.json at the repo root would arm
MemPalace's hooks on every contributor's machine the moment they open
the repo in Cursor — which would modify their conversation behaviour
without consent and write to ~/.mempalace/hook_state/ without
asking. Editor configuration is sacred; opt-in only.
If you actually want MemPalace's hooks armed when working on the MemPalace repo itself, run:
hooks/cursor/install.sh --scope project --target .
That will write ./.cursor/hooks.json for the repo workspace
specifically — but it is your decision, not ours, and the file is
listed in .gitignore paths Cursor users typically already exclude.
Related: the Cursor plugin
The hooks here are only one half of MemPalace's Cursor integration. The other half is the .cursor-plugin/ folder at the repo root, which packages MemPalace's MCP server, five slash commands, and the model-invocable mempalace skill as a regular Cursor plugin you can drop into ~/.cursor/plugins/local/mempalace.
The two install paths are orthogonal — install whichever you want, in any order:
| You want | Install |
|---|---|
MCP tools (mempalace_search, mempalace_add_drawer, …) + slash commands |
The plugin — see .cursor-plugin/README.md |
| Auto-save every N turns + sessionStart memory recall | The hooks here — see Option A above |
| Both | Install the plugin AND run hooks/cursor/install.sh |
Hooks are deliberately not bundled into the plugin because Cursor's hooks system is configured per-user/per-project (in ~/.cursor/hooks.json or .cursor/hooks.json), not per-plugin — so the installer here owns that file with idempotent merge semantics, while the plugin owns the MCP+commands+skill side.
See also
hooks/cursor/README.md— full reference for hookshooks/cursor/STDIN_SHAPE.md— per-event schema with citationswebsite/guide/cursor-hooks.md— rendered docs.cursor-plugin/README.md— Cursor plugin (MCP + commands + skill)