# NousResearch/hermes-agent · Fix transcript order in search result context windows

## Open now

- 1 issue, 0 PRs open on GitHub.
- #126762: \[Bug\] Search-result context windows are built from \`(timestamp, id)\` ordering while the transcript's canonical order is \`id\`

A bug was identified where search-result context windows used (timestamp, id) ordering instead of the transcript's canonical insertion order by id. Fixes were proposed and merged to preserve correct transcript order in search contexts.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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.

## Open related issues

- #126762: \[Bug\] Search-result context windows are built from \`(timestamp, id)\` ordering while the transcript's canonical order is \`id\`

## Prior & competing PRs

- **#126801: fix(sessions): preserve transcript order in search context**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#130173: fix(sessions): preserve transcript insertion order in search context (#126762)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#126801`

## Fix status

- No merged fix on record.
- Subsystem: `agent`