NousResearch/hermes-agent

Gateway session memory provider reuse across requests

Cluster 120116. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #120189 on 23 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #120189. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #120189. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #120189, then check it covers your case.

Read #120189 Pick up a Lab task

These members concern a bug where the gateway api_server reinitializes the memory provider on every request, preventing async memory recall from injecting into continued sessions, and a fix to share one provider per session instead.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#120189 api_server: automatic memory recall lands on continued sessions (one provider per session, #120116)

merged to main

files: agent/agent_init.py, gateway/AGENTS.md, gateway/platforms/api_server.py, gateway/platforms/api_server_memory_sessions.py, gateway/platforms/api_server_runs.py, run_agent.py, tests/agent/test_memory_provider_init.py, tests/gateway/test_api_server_memory_sessions.py, website/docs/user-guide/features/api-server.md

1 PR closed without merging

From the close comments: done elsewhere 1

#120146 fix(gateway): reuse session memory manager across api_server requests · done elsewhere → #120116, #120189

Closed issues · 1

Closed#120116gateway api_server: memory provider is re-initialised on every request (agent cache miss) so async memory recall never injects, even with X-Hermes-Session-Id continuity

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.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

Merged PRs: #120189
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/120116.json
cluster/120116.md