Cairn

Memory system proposals: scoring, forgetting, recall, and guidance

NousResearch/hermes-agent · cluster 346 · agent

Data as of

11 open items. Fix attempted, not merged.

The short answer

11open issues
0open PRs
15items grouped
Known?
Yes. 15 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
11 issues and 0 PRs. Broad area: open items may be separate problems.

Most members concern an agent's memory: what to store or forget, importance scoring, timestamps and decay, eviction, structured or cognitive recall, and memory guidance wording. A few edge items (feedback routing, multilingual extraction) are adjacent rather than clearly the same problem.

Open issues11

  • Issue#509Feature: Cognitive Memory Operations — LLM-Driven Encoding, Consolidation, Adaptive Recall & Extraction (inspired by CrewAI)
  • Issue#678Feature: Memory Extraction (Atomic Facts from Text) + Forgetting (Decay, Pruning, Targeted Purge)
  • Issue#3506Feature: Durable Feedback Routing — More Consistent Use of Memory, Skills, and Follow-Up Planning
  • Issue#9135[Feature]: Improving Multilingual Memory Extraction in Hermes
  • Issue#12883[Memory System] No importance-scoring mechanism — what should be remembered vs. forgotten?
  • Issue#15471[Feature]: Memory usage frequency tracking for smarter eviction
  • Issue#46713Feature: User correction pipeline — structured behavioral feedback that persists across sessions
  • Issue#54246MEMORY_GUIDANCE lacks a judgment test for what belongs in memory vs. what's just important
  • Issue#54247MEMORY_GUIDANCE: add routine-turn judgment test
  • Issue#61424feat(memory): add timestamps to memory entries for freshness tracking and auto-expiry
  • Issue#66654Bug: Memory pollution & stale memory accumulation — missing timestamps, priority, and data-cleaning mechanism

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #727 feat: cognitive memory system - semantic recall, encoding & forgetting · other → 70660c0, f1f25ec
  • #3507 fix: clarify durable feedback routing guidance · other
Closed issues · 2
  • Closed#346Feature: Structured Memory System — Typed Nodes, Graph Edges, and Hybrid Search
  • Closed#7896[Feature]: CerebroCortex memory provider — brain-analogous memory with associative networks, decay, and dream consolidation
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.07: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
2
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/346.json
cluster/346.md