NousResearch/hermes-agent
Token cache memory unbounded by byte size
Cluster 84727 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues 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
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug was identified where the message token-estimate cache pins raw strings including base64 data, making the entry count cap ineffective as a byte cap. The accompanying fixes add per-message byte bounds and skip oversized payloads to limit memory usage.
Open issues1
- Issue#84727[Bug] Message token-estimate cache pins raw strings incl. base64 — entry cap is not a byte cap
Open PRs1
- PR#85167fix(agent): bound message token cache memory
1 PR closed without merging
From the close comments: closed without comment 1
- #84781 fix(metadata): bound per-message token memo by pinned bytes, skip giant payloads · closed without comment
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.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging