Timmy_Foundation/hermes-agent
16
0
Fork 0
Code Issues 57 Pull Requests 3 Actions 9 Packages Projects Releases Wiki Activity

P0: Verify RetainDB Cross-Session Memory (write, recall, crash recovery) #112

New Issue
Open
opened 2026-04-06 14:06:51 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-06 14:06:51 +00:00
Owner
Copy Link

Context

Commit 6df48602 rewrote the RetainDB plugin from scratch. The previous implementation hit endpoints that returned 404 silently. The new version adds:

  • Correct API routes (/v1/context/query, /v1/memory/ingest/session, etc.)
  • SQLite write-behind queue (~/.hermes/retaindb_queue.db)
  • Background prefetch (context + dialectic synthesis + agent self-model)
  • Agent identity seeding from SOUL.md
  • Shared file store tools (upload/list/read/ingest/delete)

Acceptance Criteria

  • Verify the plugin loads: Run python -c "from plugins.memory.retaindb import RetainDBPlugin; p = RetainDBPlugin(); print(type(p).__name__)" from ~/.hermes/hermes-agent/ without import errors
  • Verify end-to-end memory write and recall: Start a CLI session, ask it to remember "Alexander's mission is caring for broken men", then start a new session and ask "what is my mission?" — it must recall from RetainDB, not from local memory
  • Verify the write queue exists: Confirm ~/.hermes/retaindb_queue.db exists after at least one turn, and SELECT COUNT(*) FROM queue shows rows were flushed
  • Verify crash recovery: Kill the agent mid-conversation (kill -9), restart, confirm pending queue rows replay on next turn
  • Verify SOUL.md ingestion: Check that AGENT-scoped memories include SOUL.md content via the retained context query API
  • Verify dialectic synthesis: Enable verbose logging and confirm dialectic query results appear in the context overlay block

Why This Matters

RetainDB cross-session memory is the technical foundation for continuity of relationship. A man who opens up at 2 AM and returns the next night deserves an agent that remembers his name, his pain, and what they talked about. Local memory is per-session; RetainDB bridges sessions permanently.

Hints

  • The RetainDB server must be reachable. Check hermes config for the retaindb endpoint.
  • The plugin is in plugins/memory/retaindb/__init__.py (792 lines).
  • File store tools: retaindb_upload_file, retaindb_list_files, retaindb_read_file, retaindb_ingest_file, retaindb_delete_file.

Parent: #111

## Context Commit `6df48602` rewrote the RetainDB plugin from scratch. The previous implementation hit endpoints that returned 404 silently. The new version adds: - Correct API routes (`/v1/context/query`, `/v1/memory/ingest/session`, etc.) - SQLite write-behind queue (`~/.hermes/retaindb_queue.db`) - Background prefetch (context + dialectic synthesis + agent self-model) - Agent identity seeding from SOUL.md - Shared file store tools (upload/list/read/ingest/delete) ## Acceptance Criteria - [ ] **Verify the plugin loads**: Run `python -c "from plugins.memory.retaindb import RetainDBPlugin; p = RetainDBPlugin(); print(type(p).__name__)"` from `~/.hermes/hermes-agent/` without import errors - [ ] **Verify end-to-end memory write and recall**: Start a CLI session, ask it to remember "Alexander's mission is caring for broken men", then start a *new* session and ask "what is my mission?" — it must recall from RetainDB, not from local memory - [ ] **Verify the write queue exists**: Confirm `~/.hermes/retaindb_queue.db` exists after at least one turn, and `SELECT COUNT(*) FROM queue` shows rows were flushed - [ ] **Verify crash recovery**: Kill the agent mid-conversation (`kill -9`), restart, confirm pending queue rows replay on next turn - [ ] **Verify SOUL.md ingestion**: Check that AGENT-scoped memories include SOUL.md content via the retained context query API - [ ] **Verify dialectic synthesis**: Enable verbose logging and confirm dialectic query results appear in the context overlay block ## Why This Matters RetainDB cross-session memory is the technical foundation for continuity of relationship. A man who opens up at 2 AM and returns the next night deserves an agent that remembers his name, his pain, and what they talked about. Local memory is per-session; RetainDB bridges sessions permanently. ## Hints - The RetainDB server must be reachable. Check `hermes config` for the retaindb endpoint. - The plugin is in `plugins/memory/retaindb/__init__.py` (792 lines). - File store tools: `retaindb_upload_file`, `retaindb_list_files`, `retaindb_read_file`, `retaindb_ingest_file`, `retaindb_delete_file`. Parent: #111
allegro commented 2026-04-06 17:00:50 +00:00
Member
Copy Link

🏷️ Automated Triage Check

Timestamp: 2026-04-06T17:00:50.301171
Agent: Allegro Heartbeat

This issue has been identified as needing triage:

Checklist

  • Clear acceptance criteria defined
  • Priority label assigned (p0-critical / p1-important / p2-backlog)
  • Size estimate added (quick-fix / day / week / epic)
  • Owner assigned
  • Related issues linked

Context

  • No comments yet — needs engagement
  • No labels — needs categorization
  • Part of automated backlog maintenance

Automated triage from Allegro 15-minute heartbeat

## 🏷️ Automated Triage Check **Timestamp:** 2026-04-06T17:00:50.301171 **Agent:** Allegro Heartbeat This issue has been identified as needing triage: ### Checklist - [ ] Clear acceptance criteria defined - [ ] Priority label assigned (p0-critical / p1-important / p2-backlog) - [ ] Size estimate added (quick-fix / day / week / epic) - [ ] Owner assigned - [ ] Related issues linked ### Context - No comments yet — needs engagement - No labels — needs categorization - Part of automated backlog maintenance --- *Automated triage from Allegro 15-minute heartbeat*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, production audit
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 blocked
Blocked by external dependency or merge conflict
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 duplicate
Duplicate of another issue
 epic
Epic - large feature with multiple sub-tasks
 gaming
Gaming agent capabilities
 infra
Infrastructure, VPS, DNS, deployment
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 morrowind
Morrowind Agent gameplay & MCP integration
 needs-review
PR or issue requires reviewer sign-off before merge/close
 p0-critical
p1-important
security
Security hardening, vulnerability fixes
 stale
No activity, pending triage or closure
 velocity-engine
Auto-generated by velocity engine
 wont-fix
Closed as intentionally not fixing — explicit descope
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#112
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?