fix: memory shows unavailable on openclaw 2026.3.28#38
Merged
Conversation
1. register memory runtime so openclaw recognizes us as active backend 2. create sqlite marker file so status check doesn't bail early 3. add prompt section telling agent not to read local memory files 4. strip openclaw sender metadata before sending to supermemory api 5. skip query param on new session for faster profile load 6. fix word boundary bug in detectCategory regexes
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
Dhravya
approved these changes
Mar 31, 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
2 participants
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.
openclaw 2026.3.28 added a formal memory plugin contract (
registerMemoryRuntime) that we weren't calling. plugin loaded fine but openclaw reported memory as unavailable.what changed:
runtime.tsregisters our plugin as the active memory backend viaregisterMemoryRuntime, so openclaw stops saying unavailable~/.openclaw/memory/main.sqlitedoesn't exist (designed for local memory plugins). we create an empty one at module load so the check passes through to our runtimeSender (untrusted metadata)json blocks. we now strip those before sending to supermemory api (matched their ownstrip-inbound-meta.tslogic)getProfile()without query param instead of searching against the startup system prompt/is|are/was matching substrings in every word, added word boundariestested on openclaw 2026.3.28,
openclaw statusnow shows0 files · 0 chunks · plugin openclaw-supermemoryinstead ofunavailable.