
from total-recall264
Autonomous agent memory that passively observes session transcripts, compresses them into prioritized notes, consolidates redundancies, and recovers missed cont
Total Recall adds a persistent, observation-driven memory layer to an agent. It periodically scans recent session transcripts, compresses them into prioritized observations, consolidates and prunes redundant items, and provides session-recovery hooks to capture missed context. Optional reactive watching makes capture near-real-time on high activity.
Use Total Recall when you want cross-session continuity without managing databases or vector indexes: long-running agents, teams needing concise memory logs, or agents that must preserve important events with minimal maintenance. It's ideal for agents that should "just pay attention" and surface prior decisions, preferences, or follow-ups.
prompts/ for Observer/Reflector.Works with agents that can run shell scripts and call LLM providers (OpenRouter, Ollama, Groq). Particularly suited to OpenClaw-style agents and cron-driven agent runs.
Total Recall is a comprehensive autonomous agent memory skill with 17 scripts covering observation compression, reflection/consolidation, session recovery, reactive watching, dream cycle, importance decay, and emergency alerting. The architecture is well-designed with 5 layers of redundancy. Scripts that ran successfully (config, tools, buffer-inject, emergency-surface, sensor-sweep, staging-review) showed clean output with proper logging and graceful degradation. 6 scripts failed due to _compat.sh source path issues in the test environment and missing jq. The skill requires OPENROUTER_API_KEY and several system deps (jq, inotify-tools, PyYAML). Security is solid — no exfiltration, no destructive commands, API keys are env-based — with minor concerns around eval-based .env loading and some string interpolation in shell commands.
jqinotify-toolspython3-yaml (PyYAML)Impressively comprehensive skill. The 5-layer redundancy (observer, reflector, session recovery, reactive watcher, pre-compaction hook) is well-architected. Dream cycle with importance decay and pattern promotion is a standout feature. Code is generally well-structured with atomic writes, lock files, dedup, and graceful degradation. The eval-based .env sourcing and some shell interpolation patterns are minor security concerns but not malicious. Scripts that need workspace context naturally fail in isolation — expected behavior.