MuninnDB Auto Memory
ReviewAudited by ClawScan on May 14, 2026.
Overview
This skill is a coherent local memory integration, but it automatically stores and reuses session context and can run a silent periodic snapshot job, so users should review its persistence behavior carefully.
Install this only if you intentionally want MuninnDB to act as an automatic long-term memory layer. Before enabling the cron job, check exactly what the snapshot script records, protect the API key, and set your own rules for confirming, reviewing, and deleting saved memories.
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.
Information from prior sessions could influence future agent behavior or preserve sensitive, incorrect, or injected content without the user noticing each time.
The skill automatically retrieves persistent memory into future sessions and automatically writes new facts, but does not provide clear safeguards for sensitive content, poisoned memories, retention, deletion, or user confirmation.
Bei jeder neuen Session: ... `mcp_muninndb_muninn_recall(...)` ... Aus dem Ergebnis: relevante Fakten in den Kontext einweben ... Speichere automatisch wichtige Fakten via `mcp_muninndb_muninn_remember`
Use only if you want automatic persistent memory; periodically review and delete MuninnDB entries, avoid storing secrets, and require confirmation before saving sensitive or high-impact facts.
If the cron job is created, local session context can continue being captured and written to memory every 30 minutes until the user pauses or removes it.
The documented workflow establishes recurring background persistence that stores context snapshots without an agent prompt and suppresses successful output.
Ein Cron-Job (`MuninnDB Memory Snapshot`) speichert alle 30 Minuten einen Kontext-Snapshot ... no_agent: true ... silent_on_success: true
Create the cron job only if you explicitly want continuous memory snapshots; verify the job list, pause/remove it when not needed, and understand what data the script records.
Anyone or any process able to use that key may be able to read or write MuninnDB memory for the configured vault.
The skill uses a local bearer token to access the MuninnDB vault. This is expected for the integration and is sent to localhost, but it grants write/read access to persistent memory.
API-Key: in `~/.muninn/openclaw.key` (Bearer-Token)
Keep the key file permission-restricted, rotate it if exposed, and ensure the token is scoped only to the intended MuninnDB vault.
Recent session details and local environment information may become part of persistent memory.
The snapshot script records working directory, hostname, timestamp, and recent Hermes session information into MuninnDB. This is disclosed and purpose-aligned, but may include private context.
RECENT_SESSIONS=$(hermes sessions list --limit 3 ...) SUMMARY="Cron-Snapshot ... Working Directory: $CWD Letzte Sessions: $RECENT_SESSIONS"
Review what `hermes sessions list --limit 3` outputs in your environment before enabling snapshots, and avoid running it in sensitive projects unless acceptable.