@2en/memory-browser
v1.1.1
Published
OpenClaw plugin that exposes the **memory directory** (all `.md` files) as **Gateway WebSocket RPC methods**.
Downloads
406
Readme
memory-browser
OpenClaw plugin that exposes the memory directory (all .md files) as Gateway WebSocket RPC methods.
What you get
Gateway methods (call via WS RPC):
memory-browser.list— List all.mdfiles in the memory directory (recursive). Returns{ files: string[] }(relative paths).memory-browser.get— Return the content of a single.mdfile. Params:{ path: string }(relative path, e.g."notes/foo.md"). Returns{ path: string, content: string }.
Memory directory
The memory directory is resolved in this order:
- Plugin config
memoryDir(absolute path) <OPENCLAW_STATE_DIR>/memory(or<CLAWDBOT_STATE_DIR>/memory)<process.cwd()>/memory
Install on a gateway host
Put this plugin on the gateway host and make it discoverable, e.g.:
- Workspace:
<workspace>/.openclaw/extensions/memory-browser/withindex.ts+openclaw.plugin.json - Or set
plugins.load.pathsto the plugin folder
- Workspace:
Enable the plugin in
openclaw.json:
{
"plugins": {
"enabled": true,
"entries": {
"memory-browser": { "enabled": true, "config": {} }
}
}
}Optional config: config.memoryDir to override the memory directory path.
Call examples (RPC params)
List all .md files:
{ "method": "memory-browser.list", "params": {} }Get one file:
{ "method": "memory-browser.get", "params": { "path": "notes/meeting-2024.md" } }path must be a relative path to a .md file inside the memory directory; directory traversal (..) is rejected.
