Sharpagent Memory System
ReviewAudited by ClawScan on May 11, 2026.
Overview
This is a coherent memory skill, but it proposes automatic long-term and permanent storage of session/task history without enough visible controls for consent, retention, deletion, or review.
Install only if you want the agent to maintain persistent memory. Before using it, decide what kinds of information it may store, where the memory files will live, how you can review and delete them, and whether scheduled background memory processing should be enabled.
Findings (2)
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.
Private or sensitive details from past conversations and tasks could be kept, summarized, merged, and surfaced in later work, potentially for longer than the user expects.
The skill is explicitly designed to retain and reuse task context and user knowledge across sessions, including unlimited/permanent layers. The visible artifact does not clearly define consent, exclusions, inspection, export, or reliable deletion controls.
L4: Contextual ... Storage: Completed task full context ... Capacity: Unlimited ... L5: Long-Term ... Storage: Persistent cross-session knowledge ... Lifespan: Permanent unless explicitly forgotten ... L6: Archive ... Lifespan: Permanent read-only
Require explicit opt-in for persistent memory, define exactly what may be stored, provide user-visible review/export/delete controls, exclude sensitive categories by default, and document whether archive entries can be permanently purged.
The agent could change what it remembers or forgets outside a direct user request, making later behavior harder to predict or verify.
The memory maintenance process is described as recurring and automatic. It can trigger consolidation, archiving, forgetting, and merging of persistent memory without clear user confirmation, stop controls, or audit requirements.
Trigger: Heartbeat (low load, every 30 min), user says "clean up", or scheduled 04:00 daily.
Make scheduled memory processing opt-in, require clear user confirmation for destructive or permanent retention changes, log all memory mutations, and provide a simple way to pause or disable background processing.