NousResearch/hermes-agent

Handling raw markdown in MEMORY.md files

Cluster 32965 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

0open issues
3open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 3 PRs.

These issues and PRs concern a bug where MEMORY.md files written as plain markdown (rather than §-delimited entries) were silently ignored or mishandled. The work explores parsing, warning, and auto-splitting strategies for such files.

Open issues0

No open issues.

Open PRs3

  • PR#32978fix: parse raw markdown memory files
  • PR#33510fix(memory): warn and accept raw markdown MEMORY.md instead of silently blocking
  • PR#33781fix(memory): auto-split raw markdown memory files by ## headings (#32965)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #33356 fix(memory): warn on oversized raw markdown imports · superseded by another PR → #32978
Closed issues · 1
  • Closed#32965Memory silently ignored when MEMORY.md is raw markdown instead of §-delimited entries
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.