Timmy_Foundation/hermes-agent
15
0
Fork 0
Code Issues 64 Pull Requests 2 Actions 1 Packages Projects Releases Wiki Activity

[SELF-IMPROVEMENT] Allegro: Upgrade memory system from entry-list to true key-value #183

New Issue
Closed
opened 2026-04-07 11:38:32 +00:00 by allegro · 1 comment
allegro commented 2026-04-07 11:38:32 +00:00
Member
Copy Link

Self-Improvement Issue

Based on review of GrepTard Agentic Memory Architecture Report. The report noted that Hermes memory is described as a 'key-value memory system' but is actually a bounded entry-list system.

Gap Identified

Current memory tool uses content-based identification (old_text) rather than true key-value storage. This makes updates and deletions inefficient and error-prone.

What's Missing

  • True key-value memory system with explicit keys
  • Fact validation and conflict detection
  • Semantic categorization/tagging of facts
  • Automatic expiration/review mechanisms

Desired State

  • Memory system with get/set/delete by explicit keys
  • Ability to store structured data (JSON) not just free text
  • Conflict detection when setting values
  • Tagging/categorization for organization
  • TTL/expiration for automatic forgetting

Acceptance Criteria

  • Design true key-value memory API (get/set/delete by key)
  • Implement fact validation (type checking, conflict detection)
  • Add semantic tagging/categorization system
  • Implement TTL/expiration mechanism
  • Ensure backward compatibility with existing memory usage
  • Test performance and reliability

Origin

Rockachopa's note on PR #525: "Make sure you live up to this, write gap issues for yourself if you dont."

## Self-Improvement Issue Based on review of GrepTard Agentic Memory Architecture Report. The report noted that Hermes memory is described as a 'key-value memory system' but is actually a bounded entry-list system. ### Gap Identified Current memory tool uses content-based identification (old_text) rather than true key-value storage. This makes updates and deletions inefficient and error-prone. ### What's Missing - True key-value memory system with explicit keys - Fact validation and conflict detection - Semantic categorization/tagging of facts - Automatic expiration/review mechanisms ### Desired State - Memory system with get/set/delete by explicit keys - Ability to store structured data (JSON) not just free text - Conflict detection when setting values - Tagging/categorization for organization - TTL/expiration for automatic forgetting ### Acceptance Criteria - [ ] Design true key-value memory API (get/set/delete by key) - [ ] Implement fact validation (type checking, conflict detection) - [ ] Add semantic tagging/categorization system - [ ] Implement TTL/expiration mechanism - [ ] Ensure backward compatibility with existing memory usage - [ ] Test performance and reliability ### Origin Rockachopa's note on PR #525: "Make sure you live up to this, write gap issues for yourself if you dont."
allegro self-assigned this 2026-04-07 11:38:33 +00:00
Timmy commented 2026-04-07 14:15:35 +00:00
Owner
Copy Link

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.
Timmy closed this issue 2026-04-07 14:15:37 +00:00
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
 epic:memory
Unified Memory Architecture epic
 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
phase:1-activate
Phase 1: Activate existing systems
 phase:2-operational
Phase 2: Operational memory bridge
 phase:3-episodic
Phase 3: Proactive episodic recall
 phase:4-hygiene
Phase 4: Memory hygiene and quality
 phase:5-integration
Phase 5: Integration and testing
 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 hermes kimi manus perplexity sonnet
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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