Install Powermem Memory

v0.2.0

Step-by-step guide to install and configure the PowerMem long-term memory plugin (full path, options, troubleshooting). After setup, the plugin auto-captures...

3· 406·0 current·0 all-time
bypowermem@teingi
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the instructions: SKILL.md is a step-by-step installer and config guide for PowerMem and the memory-powermem plugin. All required actions (checking OpenClaw, installing Python/pmem, installing the plugin, setting OpenClaw config) are directly relevant to that purpose; nothing unrelated is requested.
Instruction Scope
Instructions explicitly tell the agent/operator to run CLI commands, create/activate a Python venv, pip install powermem, and configure OpenClaw (enable plugin, set pmemPath, toggles like autoCapture/autoRecall). Those steps are within expected scope. The doc recommends enabling autoCapture/autoRecall and describes that the plugin will send conversation highlights to PowerMem and can inject memories before replies — this is central to the plugin but is a privacy-relevant behavioral detail the user should be aware of.
Install Mechanism
This is an instruction-only skill with no install spec or code files that would write/execute downloaded artifacts. It recommends using pip and optionally an install.sh from the memory-powermem repo; the doc points to the upstream GitHub INSTALL.md rather than embedding or fetching arbitrary third-party binaries. No suspicious download URLs or extraction steps are present in the SKILL.md content provided.
!
Credentials
The skill does not request any environment variables itself, which is consistent for an instruction-only guide. However, it documents and recommends useOpenClawModel: true (the default), and explains that the plugin will inject OpenClaw LLM + embedding env vars into pmem subprocess calls or server mode. That behavior is expected for an 'intelligent extraction' memory plugin, but it means provider API keys configured for the gateway may be forwarded to PowerMem (and used to call external LLM/embedding providers). Users should understand this credential flow and the privacy implications of auto-capturing conversation contents.
Persistence & Privilege
The skill does not claim always:true and is not force-included. It recommends enabling the plugin and configuring plugin settings, but does not modify unrelated skills or system-wide agent settings beyond the plugin's entries. The guide notes optional creation of ~/.openclaw/powermem/powermem.env (a per-user file) and default SQLite under the OpenClaw state dir; these are standard persistence artefacts for such a plugin.
Assessment
This guide appears internally consistent, but review these points before installing: - Privacy & auto-capture: The plugin's defaults (autoCapture=true, autoRecall=true) will automatically store conversation highlights and inject memories. If you have privacy concerns, disable autoCapture or inspect what is stored and where (default: ~/.openclaw/powermem/data/powermem.db). - Credentials flow: If you leave useOpenClawModel=true, OpenClaw’s configured model/provider credentials may be provided to PowerMem (pmem process or server) so it can call LLM/embedding services. If you prefer isolation, set useOpenClawModel=false and supply a dedicated powermem.env or separate provider keys. - Verify upstream code before running helpers: The SKILL refers to an install.sh and the memory-powermem repo. Inspect any install scripts (install.sh) and the GitHub INSTALL.md before running them to ensure they do not perform unexpected network or filesystem actions. - Prefer virtualenv and local SQLite: Follow the guide’s venv recommendation and use the default SQLite local store for personal setups to limit network exposure. For server/enterprise deployments, configure API keys and server auth carefully. - Confirm network behavior: If you install powermem or run powermem-server, check whether powermem calls remote endpoints (LLM providers, telemetry). Review powermem docs/source (linked) and run powermem-server locally with health checks before pointing the plugin at it. If you want more confidence, provide the exact install.sh referenced (or the memory-powermem repo URL you plan to use) and I can review that script for suspicious commands or network downloads.

Like a lobster shell, security has layers — review code before you run it.

latestvk9716v10wjd6j72zfthhk01g1n83gt1y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments