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

[Memory P3] Auto-trigger session search on recall patterns #249

New Issue
Open
opened 2026-04-09 00:41:35 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-04-09 00:41:35 +00:00
Owner
Copy Link

Context

Users say things like "we did this before", "last time", "remember when", "as I mentioned", "what did we decide about X" — these are recall signals that should automatically trigger session search.

Task

  1. Define pattern list for recall signals (regex or keyword)
  2. When detected, automatically invoke session_search
  3. Inject results as prefetched context (not a visible tool call)
  4. Combine with the FTS5 probe from P3.1 — patterns trigger unconditionally, probe triggers conditionally

Patterns to detect

  • "we did this before" / "we've done this" / "we already"
  • "last time" / "previously" / "earlier"
  • "remember when" / "do you remember"
  • "as I mentioned" / "as we discussed"
  • "what did we decide" / "what was the plan for"

Acceptance Criteria

  • "what did we decide about memory?" auto-surfaces relevant past sessions
  • Results appear as context, not as a tool output block
  • No false triggers on casual use of "remember" or "last"

Part of: [EPIC] Unified Memory Architecture

## Context Users say things like "we did this before", "last time", "remember when", "as I mentioned", "what did we decide about X" — these are recall signals that should automatically trigger session search. ## Task 1. Define pattern list for recall signals (regex or keyword) 2. When detected, automatically invoke session_search 3. Inject results as prefetched context (not a visible tool call) 4. Combine with the FTS5 probe from P3.1 — patterns trigger unconditionally, probe triggers conditionally ## Patterns to detect - "we did this before" / "we've done this" / "we already" - "last time" / "previously" / "earlier" - "remember when" / "do you remember" - "as I mentioned" / "as we discussed" - "what did we decide" / "what was the plan for" ## Acceptance Criteria - "what did we decide about memory?" auto-surfaces relevant past sessions - Results appear as context, not as a tool output block - No false triggers on casual use of "remember" or "last" Part of: [EPIC] Unified Memory Architecture
Rockachopa added this to the Unified Memory Architecture milestone 2026-04-09 00:41:35 +00:00
Rockachopa added the phase:3-episodicepic:memory labels 2026-04-09 00:41:35 +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 epic:memory phase:3-episodic
Milestone
No items
No Milestone Unified Memory Architecture
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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