Fix OpenClaw Supermemory onboarding#56
Merged
Merged
Conversation
Member
Author
|
@claude pls review |
MaheshtheDev
approved these changes
Jun 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the OpenClaw Supermemory npm onboarding flow so users can install the package, run setup, restart the gateway, and actually get Supermemory loaded as the active memory plugin.
What was broken
The README told npm users to run:
There were three issues:
OpenClaw did not know this plugin owned the
supermemoryCLI command.The command implementation existed in
commands/cli.ts, but the plugin manifest did not advertise ownership of thesupermemoryroot command.OpenClaw routes plugin CLI commands from cold metadata before loading the full plugin runtime, so users could see:
The plugin could be installed but not selected as the active memory plugin.
OpenClaw only allows one plugin to own the memory slot. The default slot is
memory-core, soopenclaw-supermemorycould be installed and enabled but still effectively disabled.In that state, inspection showed:
Setup granted conversation access but not prompt injection.
Auto-capture needs conversation access, but auto-recall also needs prompt injection so the plugin can inject recalled memories before an AI turn.
Agent cannot access tools
After installing the npm plugin and running setup, OpenClaw could load the plugin and route the
openclaw supermemory ...CLI command, but the main agent still could not access the Supermemory tools.openclaw supermemorysetup andopenclaw supermemory setup-advancednow add the Supermemory tools to tools.alsoAllow:{ "tools": { "alsoAllow": [ "supermemory_store", "supermemory_search", "supermemory_forget", "supermemory_profile" ] } }Also verified locally with:
The plugin reports as loaded, exposes the
supermemorycommand, and uses version2.1.14and tools also worked