NousResearch/hermes-agent

Cache key scoping and propagation fixes

Cluster 79014. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #79161 on 5 Aug 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 #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.

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

Read #79161 Pick up a Lab task

These issues and PRs address problems with prompt_cache_key being shared across sessions and not correctly propagating to the extra_body field that xAI reads. Both concerns relate to cache key isolation and routing behavior.

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#79014xAI Responses: top-level prompt_cache_key override doesn't propagate to extra_body (the field xAI actually reads)

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.

cluster/79014.json
cluster/79014.md