NousResearch/hermes-agent

Cache key session scoping and header identity issues

Cluster 79013. Data as of

Nothing open on GitHub. Fix merged in #79161 on 5 Aug 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 #79161. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #79161. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern prompt_cache_key not being scoped per session, leading to cross-session cache bucket sharing, and a related divergence between session_id/x-client-request-id headers and the body's prompt_cache_key losing physical session identity.

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.

  • #79161 fix(cache): scope prompt_cache_key by session to stop cross-session bucket sharing

    merged to main

    files: agent/auxiliary_client.py, agent/transports/chat_completions.py, agent/transports/codex.py, agent/turn_context.py, plugins/model-providers/nous/__init__.py, plugins/model-providers/openrouter/__init__.py, tests/agent/test_auxiliary_client.py, tests/agent/transports/test_chat_completions.py, tests/agent/transports/test_codex_transport.py, tests/providers/test_provider_profiles.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #78959 fix(cache): scope prompt_cache_key by session to stop cross-session bucket sharing · merged via another change → #79161
Closed issues · 1
  • Closed#79013Codex session_id/x-client-request-id headers diverge from body prompt_cache_key, and session_id header lost physical identity
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
#79161
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
5 Aug 2026

For your agent

The same facts, typed.