Add openclaw plugin#1096
Conversation
There was a problem hiding this comment.
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
/srcthe best place for this, or should it live in/integrations?
Thanks.
|
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. |
ce80999 to
db44996
Compare
sscargal
left a comment
There was a problem hiding this comment.
Mostly clarifications.
Should we consider adding some tests?
| } | ||
| }, | ||
|
|
||
| ``` |
There was a problem hiding this comment.
We should mention that this information could also be entered in the OpenClaw Plugins UI (as shown in your screenshot).
sscargal
left a comment
There was a problem hiding this comment.
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.
9f454b0 to
111e528
Compare
Tianyang-Zhang
left a comment
There was a problem hiding this comment.
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. |
e9c4cd6 to
4d9e1db
Compare
c95dd60 to
913f2d5
Compare
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.]
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
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".]