# NousResearch/hermes-agent · Memory char limits not respected from config.yaml

## Open now

- 1 issue, 2 PRs open on GitHub.
- #11665: Memory char limits ignored by CLI/MCP tool dispatch path
- PR #37102: fix(memory): honor config.yaml limits in registry-dispatched memory calls
- PR #58769: fix(memory): ensure char limit config values are cast to int

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.

## TL;DR

- 6 member(s): 1 open issue(s), 1 closed issue(s), 2 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): 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 member 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.

## Open related issues

- #11665: Memory char limits ignored by CLI/MCP tool dispatch path

## Closed / duplicate issues

- #53834: \[Bug\]: user_char_limit / memory_char_limit config changes do not take effect after gateway restart

## Prior & competing PRs

- **#11693: fix(memory): honor config.yaml limits in registry-dispatched memory calls (#11665)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#37102`
- **#18006: fix: MemoryStore respects memory_char_limit/user_char_limit from config.yaml**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#11665`
- **#37102: fix(memory): honor config.yaml limits in registry-dispatched memory calls**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `tests/tools/test_memory_tool.py`, `tools/memory_tool.py`
- **#58769: fix(memory): ensure char limit config values are cast to int**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#34059`, `#34059`
  - files: `agent/agent_init.py`, `tests/tools/test_memory_tool.py`, `tools/memory_tool_store.py`

## Fix status

- No merged fix on record.
- Subsystem: `agent`