Cairn

Memory char limit enforcement and overflow handling

NousResearch/hermes-agent · cluster 123569 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where import-agent wrote MEMORY.md up to a hardcoded 20,000-character limit instead of respecting the configured memory_char_limit, and a related change to evict oldest entries when memory overflows on add.

Open issues1

  • Issue#123569[Bug]: hermes import-agent writes MEMORY.md up to 20,000 chars, past memory.memory_char_limit; every later memory add is refused

Open PRs3

  • PR#123570fix(import-agent): merge memory entries within memory.memory_char_limit, not a hardcoded 20,000
  • PR#123643fix(import-agent): merge MEMORY.md against the profile's memory.memory_char_limit (#123569)
  • PR#127318fix(memory): evict oldest entries on add-overflow, archiving them
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.50: 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/123569.json
cluster/123569.md