# NousResearch/hermes-agent · Fix prompt-cache breakpoints lost on provider failover

## Open now

- Nothing open on GitHub.

A bug where prompt-cache breakpoints are not redecorated after a provider failover, leaving zero breakpoints when switching from a non-caching to a caching provider. The members include the bug report and two fix attempts addressing this redecorating issue.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #72869. Verify it addresses your case.
- **Recommended:** read PR #72869 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-72869`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #72626: \[Bug\]: provider failover keeps the old provider's prompt-cache decoration (0 breakpoints after cache-off to cache-on failover)

## Prior & competing PRs

- **#72869: fix(agent): redecorate prompt-cache breakpoints after provider failover (salvage #72682)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/conversation_compression.py`, `agent/conversation_loop.py`, `agent/moa_loop.py`, `agent/prompt_caching.py`, `agent/system_prompt.py`, `tests/agent/test_failover_identity.py`, `tests/agent/test_prompt_caching.py`, `tests/agent/test_system_prompt_restore.py`
- **#72682: fix(agent): redecorate prompt-cache breakpoints after provider failover**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#72869`

## Fix status

- Merged to main in PR #72869 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-07-27`.