What problem does it solve? Hermes Agent session history grows unbounded in the local SQLite database, consuming gigabytes of disk space, and users lack a safe, verified procedure for pruning old sessions, configuring retention, or diagnosing sessions that burned excessive tokens. ## Core Features & Use Cases - Session Pruning & Retention: Inspect database size with hermes sessions stats, export JSONL backups, and configure sessions.auto_prune with a chosen retention_days window. - Source-Specific Cleanup: Prune CLI and Telegram sessions on different schedules using a cron-driven script, or perform a one-time destructive CLI-only clear directly against state.db. - Session Forensics: Diagnose suspected loops and token burn by querying the sessions and messages tables and correlating with gateway.log delivery patterns. - Use Case: Your Hermes session database has grown to 6.7 GB across 35,000 sessions. Use this Skill to export a backup, enable 30-day auto-prune, run a manual prune, and verify the reclaimed space. ## Quick Start Ask the assistant to check my Hermes session database size and recommend a safe retention and pruning plan.