Cairn
NousResearch/hermes-agent

Fix group sender source in SimpleX adapter

Cluster 35045 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These issues and PRs address a bug where the group message sender is incorrectly read from chatItemMember rather than chatDir.groupMember. The changes correct which field is used to extract the group sender in the SimpleX adapter.

Open issues0

No open issues.

Open PRs1

  • PR#35046fix(simplex): extract group sender from chatDir.groupMember

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #35174 fix(simplex): read group sender from chatDir.groupMember instead of chatItemMember · stale or abandoned
Closed issues · 1
  • Closed#35045SimpleX adapter: group sender read from chatItemMember instead of chatDir.groupMember
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
gateway
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/35045.json
cluster/35045.md