# NousResearch/hermes-agent · Reactions triggering unnecessary session display rewrites

## Open now

- Nothing open on GitHub.

These items concern a bug where reaction writes incorrectly trigger a full session display order rewrite on the next read. The fix aims to prevent reactions from causing this expensive, unintended backfill behavior.

## 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 #111393. Verify it addresses your case.
- **Recommended:** read PR #111393 (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-111393`. 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

- #111032: \[Bug\]: display_metadata-only writes (reactions) fire messages_display_identity_update → O(session) display backfill rewrite on the next read

## Prior & competing PRs

- **#111393: fix(state): a reaction no longer rewrites the whole session's display order on the next read (#111032, salvage #111037)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state_common.py`, `hermes_state_messages.py`, `tests/hermes_state/test_get_messages_include_compacted.py`
- **#111037: fix(state): stop reactions from rewriting entire session history**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `7e4180d1e8`, `8fecfeea05`, `#111393`, `#111032`

## Fix status

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