Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[SELF-IMPROVE] Session DB auto-pruning — compress old sessions, enforce growth limit #1479

New Issue
Open
opened 2026-04-05 23:20:25 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-05 23:20:25 +00:00
Owner
Copy Link

Problem

hermes_state.py session DB (SQLite FTS5) grows without bound. Every conversation, tool call, response lives forever. Eventually: slow FTS5 queries, disk pressure, bloated context.

What To Do

Create ~/.hermes/bin/session-db-pruner.py:

  1. Find and connect to session DB (HERMES_HOME, likely hermes_sessions.db)
  2. Report current DB size and row count
  3. Prune rules:
    • Sessions older than 30 days: compress (keep first/last message + metadata, drop tool call details)
    • Sessions older than 90 days: delete entirely
    • Rebuild FTS5 index after pruning
  4. Run VACUUM to reclaim space
  5. Report before/after: size, rows removed, space reclaimed
  6. No active sessions affected (activity in last 7 days)

Acceptance Criteria

  • Script at ~/.hermes/bin/session-db-pruner.py exists
  • Running it outputs: DB before, rows compressed, rows deleted, DB after, space reclaimed
  • No active sessions (last 7 days) affected
  • FTS5 search still works after pruning (test with a known query)
  • Comment on epic #1474 with script path, before/after sizes, search test result

Labels: self-improve, priority-medium

Assignee: groq

## Problem hermes_state.py session DB (SQLite FTS5) grows without bound. Every conversation, tool call, response lives forever. Eventually: slow FTS5 queries, disk pressure, bloated context. ## What To Do Create ~/.hermes/bin/session-db-pruner.py: 1. Find and connect to session DB (HERMES_HOME, likely hermes_sessions.db) 2. Report current DB size and row count 3. Prune rules: - Sessions older than 30 days: compress (keep first/last message + metadata, drop tool call details) - Sessions older than 90 days: delete entirely - Rebuild FTS5 index after pruning 4. Run VACUUM to reclaim space 5. Report before/after: size, rows removed, space reclaimed 6. No active sessions affected (activity in last 7 days) ## Acceptance Criteria - [ ] Script at ~/.hermes/bin/session-db-pruner.py exists - [ ] Running it outputs: DB before, rows compressed, rows deleted, DB after, space reclaimed - [ ] No active sessions (last 7 days) affected - [ ] FTS5 search still works after pruning (test with a known query) - [ ] Comment on epic #1474 with script path, before/after sizes, search test result ## Labels: self-improve, priority-medium ## Assignee: groq
groq was assigned by Timmy 2026-04-05 23:20:25 +00:00
Timmy commented 2026-04-06 02:32:45 +00:00
Author
Owner
Copy Link

Alexander ordered: go to Issue #427 and comment on OpenProse as force multiplier. Do it now.

Alexander ordered: go to [Issue #427](https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/427) and comment on OpenProse as force multiplier. Do it now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees groq
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1479
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?