Cairn
NousResearch/hermes-agent

Split skill message cache into stable/volatile parts

Cluster 81867. Data as of

Nothing open on GitHub. Fix merged in #82423. Check it covers your case.

The short answer

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

These issues and PRs address a caching inefficiency where volatile tail bytes in skill invocation messages invalidate the entire cached prefix. The work involves declaring stable/volatile boundaries on skill turns so static prefixes can be reused across webhook events.

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.

  • #82423 perf(cache): split skill turns at a builder-declared stable/volatile boundary

    merged to main

    files: agent/prompt_cache_boundary.py, agent/prompt_caching.py, agent/skill_commands.py, cron/scheduler.py, tests/agent/test_prompt_cache_boundary.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · merged via another change 1

  • #81928 perf(cache): reuse static skill prefixes across webhook events · superseded by another PR → #82423, #82049, #81867
  • #81929 fix(agent): declare skill cache boundaries on the message · superseded by another PR → #82423, #82049, #81867
  • #82049 perf(cache): split skill turns at a builder-declared stable/volatile boundary · merged via another change → #82423, #81928, #81929
Closed issues · 1
  • Closed#81867Webhook/skill-invocation user messages cache as one atomic block — volatile tail bytes invalidate the entire static prefix
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.40: 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
#82423
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
9 Aug 2026

For your agent

The same facts, typed.

cluster/81867.json
cluster/81867.md