NousResearch/hermes-agent
flush_memories timeout config and removal discussion
Cluster 6154. Data as of
Nothing open on GitHub. Fix merged in #6361 on 9 Apr 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #6361. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #6361. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where flush_memories() uses a hardcoded 30-second timeout instead of the configured value, along with proposed fixes and a refactor to remove the function entirely.
Open issues0
Open PRs0
Fixes on record
-
#6361 fix(agent): respect config timeout for flush_memories instead of hardcoded 30s
files:
run_agent.py,tests/run_agent/test_flush_memories_codex.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#6177 fix(agent): respect config timeout for flush_memories · merged via another change →
#6361
Closed issues · 1
- Closed#6154[Bug]: flush_memories() hardcodes 30s timeout, ignores config value
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
- Merged PRs
- #6361
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 9 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.