Add openclaw plugin by malatewang · Pull Request #1096 · MemMachine/MemMachine

malatewang · 2026-02-10T22:58:29Z

Purpose of the change

Add a plugin for openclaw so that openclaw can use MemMachine as longterm memory

Description

Add a plugin for openclaw for MemMachine. The openclaw can access MemMachine through the MemMachine Typescript rest client to store and search memory.

Fixes/Closes

Fixes #(issue number)

Type of change

[Please delete options that are not relevant.]

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Refactor (does not change functionality, e.g., code style improvements, linting)
Documentation update
Project Maintenance (updates to build scripts, CI, etc., that do not affect the main project)
Security (improves security without changing functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

[Please delete options that are not relevant.]

Test Results: [Attach logs, screenshots, or relevant output]

Checklist

[Please delete options that are not relevant.]

Maintainer Checklist

Confirmed all checks passed
Contributor has signed the commit(s)
Reviewed the code
Run, Tested, and Verified the change(s) work as expected

Screenshots/Gifs

[If applicable, add screenshots or GIFs that show the changes in action. This is especially helpful for API responses. Otherwise, delete this section or type "N/A".]

Further comments

[Add any other relevant information here, such as potential side effects, future considerations, or any specific questions for the reviewer. Otherwise, type "None".]

sscargal

Some questions and requests:

Please write a User Guide, which would be very helpful for describing the steps needed to install, configure, and use this.
- Does a user need a MemMachine Platform account and an API key for this to work, or do we expect them to have MemMachine Server running locally? Or both?
How should this be distributed? (aka, how does a user install this in their environment?)
- Do we need to build and publish a separate/dedicated NPM package?
Is /src the best place for this, or should it live in /integrations?

Thanks.

integrations/openclaw/openclaw.plugin.json

integrations/openclaw/index.ts

honggyukim · 2026-02-11T03:52:43Z

Hi @malatewang, thanks for working on this.

In addition to @sscargal's comment. It would be helpful if the commit message contains more useful description rather than a single line message.

sscargal

Mostly clarifications.

Should we consider adding some tests?

sscargal · 2026-02-12T18:16:33Z

integrations/openclaw/README.md

@@ -0,0 +1,28 @@
+## Setup


Can you add an Introduction that explains what this plugin is, what it does, and how it works? It'll help users better understand what we're offering. We should include a prerequisite that users need an API Token and a free account on our MemMachine platform (See below for instructions)

Assume the reader knows nothing about MemMachine and write accordingly.

This README.md becomes the package README when published, so it needs to contain more information for the users to follow. See https://www.npmjs.com/package/@openclaw/voice-call?activeTab=readme for an example.

sscargal · 2026-02-12T18:16:57Z

integrations/openclaw/README.md

+## Setup
+
+```bash
+openclaw plugins install @memmachine/openclaw-memmachine


This installation method assumes there is a published NPM package on npmjs.com, but I don't see anywhere that we publish this package to npmjs.com using the openclaw-memmachine package name within the memmachine organization. I expect to see a GitHub Actions Workflow file that publishes the package.

Once this PR is approved and merged, and the package is published, we should have a publicly available package at https://www.npmjs.com/package/@memmachine/openclaw-memmachine.

We have other packages published to the @memmachine org, such as https://www.npmjs.com/package/@memmachine/n8n-nodes-memmachine.

https://docs.openclaw.ai/tools/plugin#cli lists many options for installing plugins. I agree that the NPM approach is the best and easiest for users.

We should recommend that the user verify the plugin is installed successfully using openclaw plugins list.

sscargal · 2026-02-12T18:24:35Z

integrations/openclaw/README.md

+          "baseUrl": "https://api.memmachine.ai",
+          "autoCapture": true,
+          "autoRecall": true,
+          "orgId": "openclaw",


Do we need the user to provide this value during initial setup/config, or is openclaw the default?

This is configured on UI

Thanks for the clarification. Suggest we update the documentation to provide guidance and the necessary steps and fields that are mandatory vs optional to help the user.

sscargal · 2026-02-12T18:24:44Z

integrations/openclaw/README.md

+          "autoCapture": true,
+          "autoRecall": true,
+          "orgId": "openclaw",
+          "projectId": "openclaw",


Do we need the user to provide this value during initial setup/config, or is openclaw the default?

Need user configuration

sscargal · 2026-02-12T18:24:51Z

integrations/openclaw/README.md

+          "projectId": "openclaw",
+          "searchThreshold": 0.5,
+          "topK": 5,
+          "userId": "openclaw"


Do we need the user to provide this value during initial setup/config, or is openclaw the default?

sscargal · 2026-02-12T18:35:52Z

integrations/openclaw/index.ts

+          return jsonResult({ action: "candidates", candidates });
+        },
+      }),
+      { name: "memory_forget" },


Should this be memory_delete? The other tools use the same names for both. Here, we register the tool with memory_delete, then use memory_forget.

sscargal · 2026-02-12T18:41:47Z

integrations/openclaw/package.json

+    "@sinclair/typebox": "^0.34.48",
+    "jiti": "^2.6.1",
+    "openclaw": "^2026.2.6",
+    "pnpm": "^10.29.2"


Do we need pnmp? This package is so small that we're unlikely to benefit from it. It would reduce the dependency count by 1, likely reducing the package's disk space. pnpm has a large dependency that inflates the storage required for this package. This is more of a curiosity than a hard requirement, so removing it is not a hard requirement. If we do need it, then there's no problem.

Recommendation - pick npm or pnpm; We don’t ship both package-lock.json and pnpm dependency

integrations/openclaw/index.ts

sscargal · 2026-02-12T18:58:20Z

integrations/openclaw/README.md

+
+### Platform (MemMachine Cloud)
+
+Get an API key from [MemMachine Cloud](https://console.memmachine.ai), then add to your `openclaw.json`:


If the only requirement is to have the user enter their apikey, perhaps clarifying that they can copy/paste this snippet into their existing openclaw.json would be helpful. I assume/understand that all the required orgId, projectId, and owner fields would then default to openclaw. Is the user free to change this in the JSON or plugin config?

I think it is easier to configure on UI?

Likely, yes. Supporting the UI and 'manual' methods is okay with me

If the user needs to copy/paste the JSON snippet anyway, including this 'manual' method is fine.

If the user doesn't need to copy/paste into their master openclaw.json, then documenting the UI approach is better.

Not necessary. I think once the npm is installed, the entry is added automatically to the openclaw.json and it is disabled. The user just need to fill the value.

sscargal · 2026-02-12T18:58:28Z

integrations/openclaw/README.md

+        }
+      },
+
+```


We should mention that this information could also be entered in the OpenClaw Plugins UI (as shown in your screenshot).

sscargal

We could consider whether it's worth moving this to a dedicated repository. It may be easier to maintain and version control independently. Just an idea, not a request.

sscargal · 2026-02-19T23:16:59Z

integrations/openclaw/README.md

+
+```bash
+openclaw plugins install ./memmachine/openclaw
+cd ./memmachine/openclaw && pnpm install


Should the memmachine/openclaw directory not be integrations/openclaw?

sscargal · 2026-02-19T23:20:05Z

integrations/openclaw/README.md

We could use https://www.npmjs.com/package/@supermemory/openclaw-supermemory as a guiding flow for this README.

Should we consider if a slash command or CLI is necessary, similar to SuperMemory?

We do support CLI commands. I updated the README

sscargal · 2026-02-19T23:21:45Z

integrations/openclaw/README.md

Should we consider if a slash command or CLI is necessary, similar to SuperMemory?

Tianyang-Zhang

I see the memmachine API Key have some usage limits. Can't I use my own OpenAI API keys and AWS reranker key?

malatewang · 2026-02-20T18:41:01Z

I see the memmachine API Key have some usage limits. Can't I use my own OpenAI API keys and AWS reranker key?

The API key is for MemMachine platform. It is required only if you use the platform.

sscargal requested changes Feb 11, 2026

View reviewed changes

malatewang force-pushed the openclaw branch from abdb49b to d4de419 Compare February 11, 2026 01:29

1saac-k reviewed Feb 11, 2026

View reviewed changes

integrations/openclaw/openclaw.plugin.json Outdated Show resolved Hide resolved

1saac-k reviewed Feb 11, 2026

View reviewed changes

integrations/openclaw/index.ts Outdated Show resolved Hide resolved

malatewang force-pushed the openclaw branch 3 times, most recently from ce80999 to db44996 Compare February 12, 2026 01:36

sscargal requested changes Feb 12, 2026

View reviewed changes

sscargal added the Integration An integration into a 3rd party framework or solution using MemMachine label Feb 12, 2026

malatewang force-pushed the openclaw branch from db44996 to 0eebbd0 Compare February 19, 2026 23:09

malatewang requested review from edwinyyyu, o-love and sscargal February 19, 2026 23:11

sscargal requested changes Feb 19, 2026

View reviewed changes

integrations/openclaw/README.md

Copy link

Contributor

sscargal Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider if a slash command or CLI is necessary, similar to SuperMemory?

malatewang force-pushed the openclaw branch from 0eebbd0 to 234be66 Compare February 19, 2026 23:25

o-love approved these changes Feb 20, 2026

View reviewed changes

malatewang force-pushed the openclaw branch 2 times, most recently from 9f454b0 to 111e528 Compare February 20, 2026 01:14

Tianyang-Zhang reviewed Feb 20, 2026

View reviewed changes

Add openclaw plugin

fde6483

malatewang force-pushed the openclaw branch from 0f6f65f to fde6483 Compare February 20, 2026 18:46


		### Platform (MemMachine Cloud)

		Get an API key from [MemMachine Cloud](https://console.memmachine.ai), then add to your `openclaw.json`:

+                      }
+                    },
+              ```

Conversation

malatewang commented Feb 10, 2026

Purpose of the change

Description

Fixes/Closes

Type of change

How Has This Been Tested?

Checklist

Maintainer Checklist

Screenshots/Gifs

Further comments

Uh oh!

sscargal left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

honggyukim commented Feb 11, 2026

Uh oh!

sscargal left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sscargal left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Tianyang-Zhang left a comment

Choose a reason for hiding this comment

Uh oh!

malatewang commented Feb 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

sscargal left a comment •

edited

Loading