Latest release: v1.9.1Download zip
Capabilities
Compatibility
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description say 'sidecar memory capture' and the repo documents, plugin JSON, TypeScript extension, CLI, and ingestion scripts all implement that purpose. Files (plugin, CLI, docs, tests) align with the claimed functionality; nothing asks for unrelated cloud or admin credentials.
Instruction Scope
SKILL.md focuses on local capture → JSONL → SQLite ingest and safe adoption paths. It includes operator-level instructions (git clone, uv sync, uv run, systemd/cron examples) and examples of configuring OpenClaw cron jobs that send agent-turn payloads which execute local commands (e.g., run harvest via an exec). That is coherent for an operator-run ingestion workflow but worth noting: the docs show examples where scheduled agent messages will instruct the system to run local exec commands — this is expected for OpenClaw automation but operators should verify those cron/agent payloads before enabling in production.
Install Mechanism
No automatic install spec is included; the bundle is distributed as repo files and docs instruct manual git clone / uv sync / plugin symlink. No opaque downloads, URL shorteners, or remote extract/install steps are present in SKILL.md. The included Node/Python project files are expected for the plugin and CLI.
Credentials
No required env vars or secrets are declared. Optional environment examples (e.g., OPENCLAW_MEM_IMPORTANCE_SCORER, OPENCLAW_STATE_DIR) are reasonable operator controls for behavior tuning, not undisclosed credentials. The docs do reference using model names in cron payloads (e.g., 'google-antigravity/gemini-3-flash') but do not request API keys from unrelated services.
Persistence & Privilege
always:false and user-invocable:true (defaults) — the skill does not request forced permanent inclusion. It instructs operators to add a symlink into plugin dirs or to enable plugin in OpenClaw config, which is normal for a plugin. Operators should be cautious about promoting the optional 'mem-engine' to become the active memory-slot backend (docs emphasize this is a controlled, post-proof step).
Assessment
This bundle appears to do what it says: a sidecar capture + local CLI/SQLite proof path. Before installing: (1) run the local proof steps (sample JSONL → ingest → search/timeline) on a throwaway DB to verify redaction/behavior; (2) review any systemd/cron or OpenClaw cron job snippets — they include agentTurn payloads that will cause execs to run, so only enable them if you trust the configured commands and host; (3) do not promote the optional mem-engine to own the memory slot until you've audited receipts and rollback paths. If you want extra caution, keep captureMessage and episodes disabled and rely on manual CLI ingest until comfortable.Verification
Tags
OpenClaw Mem
Sidecar-first memory capture for OpenClaw.
This ClawHub bundle installs the lightweight openclaw-mem observation plugin, not the optional memory-slot engine. It is the safest default adoption path: capture OpenClaw activity into local JSONL, ingest it into the openclaw-mem SQLite sidecar, and keep your current OpenClaw memory backend untouched.
What this bundle includes
extensions/openclaw-mem/, the sidecar capture plugin.- Operator docs for setup, deployment, auto-capture, and the optional engine path.
- No forced memory-slot migration.
- No schema migration.
- No remote service requirement for the sidecar path.
What the sidecar does
- Captures tool results into append-only JSONL for later ingest.
- Optionally spools bounded episodic events, including conversation/tool/ops events.
- Redacts common secrets by default before persistence.
- Annotates memory-tool activity so retrieval and backend behavior remain auditable.
- Lets you run local recall, timeline, graph, drift, provenance, and optimization review workflows from the GitHub repo.
Install from ClawHub
openclaw bundles install clawhub:openclaw-mem-lyria
Then enable the plugin entry in your OpenClaw config and restart/reload your gateway using your normal OpenClaw deployment path.
Minimal config shape:
{
"plugins": {
"entries": {
"openclaw-mem": {
"enabled": true,
"config": {
"outputPath": "memory/openclaw-mem-observations.jsonl",
"captureMessage": false,
"redactSensitive": true,
"backendMode": "auto",
"annotateMemoryTools": true,
"excludeAgents": ["cron-watchdog", "healthcheck"],
"episodes": {
"enabled": false,
"outputPath": "memory/openclaw-mem-episodes.jsonl"
}
}
}
}
}
}
Recommended adoption path
- Install this sidecar bundle. Keep your existing OpenClaw memory slot.
- Capture to local JSONL. Start with
captureMessage: falseandredactSensitive: true. - Run a local proof from GitHub. Clone the repo and ingest a small sample into SQLite.
- Schedule harvest / review only after the proof passes. Keep outputs in directories you control.
- Consider the engine later. Only promote to
openclaw-mem-enginewhen you want it to own the OpenClaw memory slot.
Local proof, no OpenClaw config change
git clone https://github.com/phenomenoner/openclaw-mem.git
cd openclaw-mem
uv sync --locked
DB=/tmp/openclaw-mem.sqlite
python3 ./scripts/make_sample_jsonl.py --out /tmp/openclaw-mem-sample.jsonl
uv run --python 3.13 --frozen -- python -m openclaw_mem --db "$DB" --json status
uv run --python 3.13 --frozen -- python -m openclaw_mem --db "$DB" --json ingest --file /tmp/openclaw-mem-sample.jsonl
uv run --python 3.13 --frozen -- python -m openclaw_mem --db "$DB" --json search "OpenClaw" --limit 5
uv run --python 3.13 --frozen -- python -m openclaw_mem --db "$DB" --json timeline 2 --window 2
uv run --python 3.13 --frozen -- python -m openclaw_mem --db "$DB" --json optimize review --limit 200
Engine path
The optional openclaw-mem-engine is intentionally not the default marketplace install path. It is a stronger posture because it can become the active memory-slot backend and enable hybrid recall / controlled automation.
Install it from GitHub after reading the docs:
- Repo: https://github.com/phenomenoner/openclaw-mem
- Engine docs:
docs/mem-engine.md - Deployment docs:
docs/deployment.md - Release notes: https://github.com/phenomenoner/openclaw-mem/releases
Rollback
Disable or remove the plugins.entries.openclaw-mem entry. Because this bundle is sidecar-only, your native memory backend remains untouched.
Version
This ClawHub release tracks openclaw-mem v1.9.1, including the runtime latency improvements in sidecar-adjacent retrieval workflows and the current sidecar plugin contract.