Session Guardian — Never Lose a Conversation Again

Never lose a conversation again. Auto-backup, smart recovery, and health monitoring for OpenClaw sessions. Protects against gateway crashes, model disconnect...

What to check before installing: 1) Inspect scripts/install.sh and scripts/*.sh yourself (or with a trusted admin) before running — install.sh will add cron jobs that run frequently and will read all session files under ~/.openclaw/agents. 2) Open and edit config.sh defaults before deployment: - Set DELIVERY_ENABLED=false (default is true) if you do not want any automatic push of summaries/backups to chat channels or external endpoints. - Ensure REMOTE_SYNC_ENABLED=false unless you deliberately want to sync backups to a remote host; if you do, provide and verify credentials securely. - If you want backups encrypted, set ENCRYPTION_ENABLED=true and configure GPG_KEY_ID before running. - If you do not want token/LLM usage, disable KNOWLEDGE_EXTRACTION_ENABLED and any SUMMARY_MODEL settings (SKILL.md's "zero token cost" claim is inconsistent with these enabled defaults). 3) Confirm required system tools are present (jq, rsync or rclone, gzip/pigz, cron) — the package scripts use jq and rsync-like behavior but the skill metadata declares no required binaries. 4) Run installation in a safe environment or test account first (to confirm behavior and verify no unintended pushes or remote syncs occur). 5) Audit the backup directory permissions (~/.openclaw/workspace/Assets/SessionBackups) and logs after a test run; verify backups are stored where you expect and not transmitted externally. 6) If you need stronger guarantees, ask the maintainer for minimal configuration examples that explicitly disable delivery/remote sync and LLM calls, and for a signed release or repository URL to verify provenance.

Type: OpenClaw Skill Name: session-guardian Version: 3.1.0 The session-guardian skill bundle is a comprehensive backup and monitoring utility that requires high-risk capabilities, including broad read access to all agent session logs (conversation history) and modification of the system crontab for persistence (install.sh). It also contains potential shell injection vulnerabilities in scripts like plan-manager.sh and install.sh, where un-sanitized variables are used in sed or eval commands. While these behaviors are aligned with the stated purpose of protecting session data and monitoring agent health, the combination of system-level modifications and access to sensitive data warrants a cautious classification.