Cairn
NousResearch/hermes-agent

Fix transcript order in search result context windows

Cluster 126762 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

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.

Open issues1

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

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1

  • #126801 fix(sessions): preserve transcript order in search context · closed without comment
  • #130173 fix(sessions): preserve transcript insertion order in search context (#126762) · superseded by another PR → #126801
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.67: 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

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/126762.json
cluster/126762.md