Cairn

Memory char limits not respected from config.yaml

NousResearch/hermes-agent · cluster 11665 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue 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
1 issue and 2 PRs.

A bug where user_char_limit and memory_char_limit settings in config.yaml are ignored by certain dispatch paths, including registry, CLI, and MCP tool routes. Several fixes address casting, propagation, and enforcement of these config values.

Open issues1

  • Issue#11665Memory char limits ignored by CLI/MCP tool dispatch path

Open PRs2

  • PR#37102fix(memory): honor config.yaml limits in registry-dispatched memory calls
  • PR#58769fix(memory): ensure char limit config values are cast to int

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #11693 fix(memory): honor config.yaml limits in registry-dispatched memory calls (#11665) · superseded by another PR → #37102
  • #18006 fix: MemoryStore respects memory_char_limit/user_char_limit from config.yaml · duplicate → #11665
Closed issues · 1
  • Closed#53834[Bug]: user_char_limit / memory_char_limit config changes do not take effect after gateway restart
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.29: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/11665.json
cluster/11665.md