Scope prompt cache keys to prevent cross-session sharing
NousResearch/hermes-agent · cluster 78941
Data as of
Nothing open on GitHub. Fix merged in #79161. Check it covers your case.
The short answer
- Known?
- Yes. 6 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 issues and PRs address a problem where prompt cache keys based only on content can cause unrelated sessions to share the same cache routing scope. The proposed fixes namespace or scope cache keys by session or conversation lineage to isolate them properly.
Open issues0
Open PRs0
Fixes on record
-
#79161 fix(cache): scope prompt_cache_key by session to stop cross-session bucket sharing
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 -
#79193 fix(state): stop delegate/tool children corrupting compression lineage
files:
hermes_state.py,tests/hermes_state/test_session_md_export.py
3 PRs closed without merging
From the close comments: merged via another change 2 · done elsewhere 1
-
#78956 fix(agent): namespace prompt_cache_key with logical session scope · done elsewhere →
#78941,#79161,#79017 -
#78959 fix(cache): scope prompt_cache_key by session to stop cross-session bucket sharing · merged via another change →
#79161 -
#79024 fix(cache): scope prompt cache keys to conversation lineages · merged via another change →
#79193,#78941,#79161,#78959,#79017,#78956
Closed issues · 1
- Closed#78941[Cache]: content-only prompt_cache_key can concentrate unrelated sessions into one routing scope
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.33: 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 Lab