Supermemory Free
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
The Supermemory store/search features match the stated purpose, but the auto-capture cron can upload sensitive memory-log lines, including API-key or environment-variable-looking content, to cloud storage without per-item review.
Install only if you are comfortable sending selected OpenClaw memory-log content to Supermemory.ai. Start with manual store/search or auto_capture.py --dry-run, avoid storing secrets in memory logs, and do not enable the daily cron until credential redaction and review controls are improved.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A memory log line containing an API key, configuration value, service endpoint, user preference, or other private detail could be persisted to third-party cloud memory and later retrieved or reused.
Auto-capture marks env-var/config and API-key-looking memory-log lines as high-value, then uploads the raw content field to Supermemory. The shown skip rules exclude some password/secret/token forms but do not reliably exclude API-key or env-var values.
(r"(?:/[a-z][^\s,;]{4,}|[A-Z_]{3,}=\S{3,})", "config"), ... (r"\bapi[\s_-]?key\b.{5,}", "credential"), ... "content": contentDo not enable auto-capture until it has strict redaction/denylist rules for all credentials and env-var patterns. Use --dry-run first and manually approve only non-sensitive items.
After installation, memory-log content may continue being sent to Supermemory every day until the cron job is removed.
Installing the cron script creates a persistent daily job that runs auto_capture.py and uploads recent memory-log insights without a user present.
CRON_CMD="$CRON_SCHEDULE cd $WORKSPACE_DIR && source .env && $PYTHON $SKILL_DIR/auto_capture.py --days 3 >> $LOG_FILE 2>&1 # $CRON_MARKER"
Prefer manual store/search or dry-run mode. If cron is needed, review the captured output regularly, add redaction, and confirm the remove/status commands work.
A malformed or compromised .env file could cause unexpected commands to run under the daily cron job.
The cron command sources .env as shell code to load the API key. This is a common shortcut, but it means any shell commands in that .env file would execute when the cron runs.
cd $WORKSPACE_DIR && source .env && $PYTHON $SKILL_DIR/auto_capture.py --days 3
Keep .env trusted and simple, or change the script to parse only SUPERMEMORY_OPENCLAW_API_KEY instead of sourcing the whole file.
On a shared or compromised machine, another local process/user might briefly observe the Supermemory bearer token.
The Supermemory API key is expected for this integration, but store/search pass it to curl as a command-line argument, which may be visible to local process inspection while curl runs.
f"Authorization: Bearer {api_key}" ... subprocess.run(cmd, capture_output=True, text=True)Use this only on trusted machines, protect the API key, and consider passing credentials through stdin/config or urllib rather than curl command arguments.